thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.4 2010-10-27T22:38:16Z 2010-10-27T22:38:16Z Carl Worth cworth@cworth.org 2010-10-27T22:38:16Z urn:sha1:65f2e61f28a0f5c5dc38dd3cf8a1de023934b330 It is now possible to set configuration items from the command-line in a manner quite similar to the support for querying configuration items. 2010-10-27T20:26:32Z Carl Worth cworth@cworth.org 2010-10-27T20:26:32Z urn:sha1:49d90ede87e355b086618c647d19e696b9f7069a 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). 2010-10-27T20:02:17Z Carl Worth cworth@cworth.org 2010-10-27T20:02:17Z urn:sha1:b9eac48c22f53f84ed1d9c1d8ca862a7b638c9ac So far, we implement only "notmuch config get". It won't be too much work from here to also implement "notmuch config set". 2010-07-20T00:16:18Z Carl Worth cworth@cworth.org 2010-07-20T00:16:18Z urn:sha1:676d25111e1343ce31cb4a51b26f05a06305cda5 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. 2010-04-23T17:29:28Z Carl Worth cworth@cworth.org 2010-04-23T17:29:28Z urn:sha1:c63b6473ca6b391dc858672cf36f56ec0baf3e35 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. 2010-04-23T16:28:45Z Carl Worth cworth@cworth.org 2010-04-23T16:28:45Z urn:sha1:444923e2d0ddbf7c3890296354aebdb54f1efda8 Specifically mentioning that it's a list separated by ';' and use "will" instead of "should". 2010-04-23T16:20:40Z Carl Worth cworth@cworth.org 2010-04-23T16:20:40Z urn:sha1:15e71cfda732c20d06f0a15b2ab16a940ecd5962 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. 2010-04-23T16:19:52Z Carl Worth cworth@cworth.org 2010-04-23T16:19:52Z urn:sha1:65d278afb1174a4005a613cca8c306289b195876 To eliminate a compiler warning. 2010-04-23T15:41:59Z Ben Gamari bgamari.foss@gmail.com 2010-03-12T22:13:26Z urn:sha1:143d43687410aefec7988e2d785a63c60c6062b5 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. 2010-04-21T22:54:03Z Carl Worth cworth@cworth.org 2010-04-21T22:54:03Z urn:sha1:f41a35e2923b0b3ef2f66e91cd30e20b4c1a336a 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.