notmuch/notmuch-setup.c, branch 0.2 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.2 2009-12-01T16:06:09Z notmuch setup: Exit if EOF is encountered at any prompt. 2009-12-01T16:06:09Z Carl Worth cworth@cworth.org 2009-12-01T16:06:09Z urn:sha1:eb0cf86c7a9d5cda464d4d36a9cac66f26b5529d If the user is explicitly providing EOF, then terminating the program is the most likely desired thing to do. This also avoids undefined behavior from continuing with an uninitialized response after ignoring the return value of getline(). modify notmuch_setup_command to return 1 if config file write fails. 2009-11-26T03:24:27Z Jameson Graef Rollins jrollins@finestructure.net 2009-11-22T21:58:35Z urn:sha1:34c840a23e1db4c6cf4a836b441d027fc17e9706 This fixes a small bug in notmuch_setup_command such that it returned OK and output the setup message footer even if the config file write step failed. Support multiple configuration files via $NOTMUCH_CONFIG 2009-11-23T02:01:57Z Alec Berryman alec@thened.net 2009-11-22T05:18:26Z urn:sha1:91d1d3f043b82d5f3f8c04f2db71a829a7406131 If present, $NOTMUCH_CONFIG will be used as the configuration file location. notmuch new: Unbreak after the addition of notmuch-config. 2009-11-12T03:50:15Z Carl Worth cworth@cworth.org 2009-11-12T03:50:15Z urn:sha1:37bdd8987094220c84ec39f8f550753219f68bd4 Pull in the code from add-files.c now that notmuch_new_command is the only user, (we no longer have notmuch_setup_command adding any messages). notmuch: Move welcome messages from "notmuch" to "notmuch setup". 2009-11-12T01:33:31Z Carl Worth cworth@cworth.org 2009-11-12T01:33:31Z urn:sha1:6bd01e1b340f6a209dde64471bc9d7137511dada 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. notmuch: Add a configuration system. 2009-11-12T01:01:55Z Carl Worth cworth@cworth.org 2009-11-12T01:01:55Z urn:sha1:305e76bc0ab2e7f3bd1ff2580e8d5dac8b4a7164 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. notmuch setup: Break the implementation up into manageable functions. 2009-11-11T19:23:55Z Carl Worth cworth@cworth.org 2009-11-11T19:23:55Z urn:sha1:69611e66a589881bf4de9786d3f6df991c604f3d The notmuch_setup_command function was getting entirely unwieldy. Break it up into smaller functions for better maintainability. notmuch: Break notmuch.c up into several smaller files. 2009-11-10T20:03:05Z Carl Worth cworth@cworth.org 2009-11-10T20:03:05Z urn:sha1:50144f95cababfb73027ca95ad1fb303c235a893 Now that the client sources are alone here in their own directory, (with all the library sources down inside the lib directory), we can break the client up into multiple files without mixing the files up. The hope is that these smaller files will be easier to manage and maintain.