| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
It is now possible to set configuration items from the command-line in
a manner quite similar to the support for querying configuration
items.
|
| |
|
|
|
|
| |
We might as well be general here, and allow the "notmuch config" command
to query any stored value from the configuration file, (whether or not
the rest of the code actually knows anything about that value).
|
| |
|
|
|
| |
So far, we implement only "notmuch config get". It won't be too much
work from here to also implement "notmuch config set".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit f41a35e2923b0b3ef2f66e91cd30e20b4c1a336a running a command
such as:
NOTMUCH_CONFIG=/new/config/file notmuch setup
would result in a segmentation fault.
The purpose of that commit was to ensure that an attempt to manipulate
a non-standard database would not inadvertently manipulate the default
database only due to a typo in the NOTMUCH_CONFIG environment
variable. That is, a command like:
NOTMUCH_CONFIG=mistyped-config-filename notmuch tag -new tag:new
shouldn't modify the database at ${HOME}/mail, but should instead
simply report that the mistype configuration filename does not exist.
We fix both cases simultaneously by reporting the error message
whenever the function calling notmuch_config_open is not explicitly
prepared for a default configuration file.
|
| |
|
|
|
|
| |
I think one configuration group for each top-level command makes a lot
of sense. And this makes the existing naming of set_new_tags and
get_new_tags also very reasonable.
|
| |
|
|
|
| |
Specifically mentioning that it's a list separated by ';' and use
"will" instead of "should".
|
| |
|
|
|
|
|
|
|
|
| |
Our intent has always been that when new configuration-file settings
are created by notmuch, that they get created with comments telling
the user how to use them. But this was only working before when the
entire configuration file was created.
We fix this so that when a new group is added, (such as the recently-
added [messages] section) that it gets its documentation.
|
| |
|
|
| |
To eliminate a compiler warning.
|
| |
|
|
|
|
| |
Add a new_tags option in the [messages] section of the configuration
file to allow the user to specify which tags should be added to new
messages by notmuch new.
|
| |
|
|
|
|
|
|
| |
When there is no configuration file at all, (and none specified),
notmuch works correctly by assuming correct default values. But when
the user specifies a configuration file (with the NOTMUCH_CONFIG
environment variable) and that file doesn't exist, then notmuch should
aboirt and let the user know about the problem.
|
| |
|
|
| |
Signed-off-by: Dirk-Jan C. Binnema <djcb.bulk@gmail.com>
|
| |
|
|
|
| |
If present, $NOTMUCH_CONFIG will be used as the configuration file
location.
|
| |
|
|
|
|
|
| |
While talloc is great we need to free the g_error by hand.
Tested-by: Stefan Schmidt <stefan@datenfreihafen.org>
Signed-off-by: Holger Freyther <zecke@selfish.org>
|
| | |
|
| |
|
|
|
|
| |
It's quite possible for someone to read the documentation and run
"notmuch setup" rather than just "notmuch". In that case, we don't
want to be any less welcoming.
|
| |
|
|
|
| |
The "notmuch setup" command is nice and all, but we also want to allow
users to conveniently edit the configuration file directly.
|
|
|
This will allow for things like the database path to be specified
without any cheesy NOTMUCH_BASE environment variable. It also will
allow "notmuch reply" to recognize the user's email address when
constructing a reply in order to do the right thing, (that is, to use
the user's address to which mail was sent as From:, and not to reply
to the user's own addresses).
With this change, the "notmuch setup" command is now strictly for
changing the configuration of notmuch. It no longer creates the
database, but instead instructs the user to call "notmuch new" to do
that.
|
Carl Worth
Ben Gamari
Dirk-Jan C. Binnema
Alec Berryman
Holger Freyther
Alexander Botero-Lowry