| Age | Commit message (Collapse) | Author |
|---|
|
In order to open the database in main() for this command, we may need
to re-open it in the (possibly less common) case where crypto options
require write access.
|
|
In addition to the same type of changes as converting other
subcommands, add the possibility of creating a database at the top
level. It would probably make sense to use this for insert as well.
|
|
Switch to the newly created API function notmuch_database_compact_db,
which takes the database opened in main().
|
|
In addition to changing configuration access, change talloc context
for allocation.
|
|
This will need some cleanup when the transition completes, and we stop
passing notmuch_config_t structs to the subcommands.
Unlike the general case, we open the database in the subcommand, since
we don't know whether it should be opened read/write until we parse
the command line arguments.
Add a test to make sure passing config file on the command line is not
broken by these or future config related changes.
|
|
Since we are already passing a search context around as a kind of
parameter block, add a new talloc context to that to replace relying
on 'config'.
Convert notmuch-search and notmuch-address at the same time, because
they share some code.
Add a test to make sure we don't break passing configuration as a
command line argument.
|
|
This is messier than some of the other conversions because the
extensive use of 'config' as a talloc context.
|
|
The only non-trivial part is switching the talloc context for
query_string_from args from 'config' to 'notmuch'.
|
|
The new talloc context is needed to run the hook at the very end of
the function. That in turn is needed so that this process gives up the
write lock on the database.
|
|
Switch one configuration check to new n_c_get_bool function, and
switch use of config as talloc context to notmuch.
|
|
This conversion is trivial because the only configuration information
accessed by dump is that stored in the database (in order to dump
it). We do need to be careful to keep the write lock on the database
to ensure dump consistency.
|
|
The main effort is changing from the old argv style config list
iterators to the new more opaque ones provided by the library (and
backed by the database+file config cache).
|
