thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.5 2010-11-12T04:39:22Z 2010-11-12T04:39:22Z Carl Worth cworth@cworth.org 2010-11-12T04:39:22Z urn:sha1:a68334258a14a50d942fa2f2824d37008d2443e6 It has been very difficult to get all of these right. I would not be surprised if I've still missed some. 2010-11-11T12:28:01Z Carl Worth cworth@cworth.org 2010-11-11T12:28:01Z urn:sha1:89954b453c7b97a5d173bb87f3f2bbc0510425c2 The intent of "notmuch setup" is that it adds new, documented sections to configuration files that were created before such sections were defined. But to make this work, we have to explicitly set an option in the maildir group if it didn't exist previously. 2010-11-11T12:11:21Z Carl Worth cworth@cworth.org 2010-11-11T12:11:21Z urn:sha1:28708d2bd399ed1dc7968918833df3683c7accec This is a useful feature that most people should want, so enable it by default, (still allowing customization to disable it of course). 2010-11-11T12:06:23Z Carl Worth cworth@cworth.org 2010-11-11T12:06:23Z urn:sha1:937ecd5057659474aa3f7ffe9d2a5d850a641567 Including details on which actual flags are synchronized with which tags. 2010-11-11T11:40:19Z Carl Worth cworth@cworth.org 2010-11-11T00:26:14Z urn:sha1:4cfb2a02778bac16e785bbea1fd6c665e34bd955 Since the name of the configuration parameter here is: maildir.synchronize_flags the convention is that the functions to get and set this parameter should match it in name. Hence: notmuch_config_get_maildir_synchronize_flags etc. (as opposed to notmuch_config_get_maildir_sync). 2010-11-10T21:09:32Z Michal Sojka sojkam1@fel.cvut.cz 2010-10-31T21:29:17Z urn:sha1:d9d3d3e6f06a76dc0fbe24c9655b64acfcd4b9e4 This adds group [maildir] and key 'synchronize_flags' to the configuration file. Its value enables (true) or diables (false) the synchronization between notmuch tags and maildir flags. By default, the synchronization is disabled. 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.