Summary
--search currently has no default — when omitted, the source set is decided per query. Users who consistently want a fixed non-default source set have no configuration knob; the only option is to patch SKILL.md's engine-invocation line to hardcode --search=....
A patched SKILL.md is fragile — every upstream release re-introduces the same merge point to re-apply.
Proposal
A way to set the default --search source set via configuration, so it survives upgrades. Options, roughly in order of invasiveness:
- An env var, e.g.
LAST30DAYS_DEFAULT_SEARCH=reddit,x,youtube,..., read in lib/env.py and used as the --search default when the flag is omitted.
- An argparse
default= for --search sourced from that env var or a config-file key.
- A key in
~/.config/last30days/.env, alongside the existing INCLUDE_SOURCES / EXCLUDE_SOURCES.
INCLUDE_SOURCES / EXCLUDE_SOURCES already exist as additive/subtractive knobs, so a "default set" key would slot in naturally next to them.
Question before any PR
Happy to send a PR — but the design is yours to call: env var vs config-file key vs argparse default, naming, and precedence relative to INCLUDE_SOURCES/EXCLUDE_SOURCES. Is this something you'd want, and if so which shape do you prefer?
Summary
--searchcurrently has no default — when omitted, the source set is decided per query. Users who consistently want a fixed non-default source set have no configuration knob; the only option is to patchSKILL.md's engine-invocation line to hardcode--search=....A patched
SKILL.mdis fragile — every upstream release re-introduces the same merge point to re-apply.Proposal
A way to set the default
--searchsource set via configuration, so it survives upgrades. Options, roughly in order of invasiveness:LAST30DAYS_DEFAULT_SEARCH=reddit,x,youtube,..., read inlib/env.pyand used as the--searchdefault when the flag is omitted.default=for--searchsourced from that env var or a config-file key.~/.config/last30days/.env, alongside the existingINCLUDE_SOURCES/EXCLUDE_SOURCES.INCLUDE_SOURCES/EXCLUDE_SOURCESalready exist as additive/subtractive knobs, so a "default set" key would slot in naturally next to them.Question before any PR
Happy to send a PR — but the design is yours to call: env var vs config-file key vs argparse default, naming, and precedence relative to
INCLUDE_SOURCES/EXCLUDE_SOURCES. Is this something you'd want, and if so which shape do you prefer?