notmuch - thread-based email index, search and tagging

	Commit message (Collapse)	Author	Age
*	notmuch setup: Prompt for tags to set on new messages.	Carl Worth	2010-04-23
\| \| \| \| \|	Our "notmuch setup" command is only really helpful if it guides the user through all the possible options. So add this one.
*	notmuch setup: Exit if EOF is encountered at any prompt.	Carl Worth	2009-12-01
\| \| \| \| \| \| \|	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.	Jameson Graef Rollins	2009-11-25
\| \| \| \| \| \|	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	Alec Berryman	2009-11-23
\| \| \| \| \|	If present, $NOTMUCH_CONFIG will be used as the configuration file location.
*	notmuch new: Unbreak after the addition of notmuch-config.	Carl Worth	2009-11-11
\| \| \| \| \| \|	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".	Carl Worth	2009-11-11
\| \| \| \| \| \|	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.	Carl Worth	2009-11-11
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.	Carl Worth	2009-11-11
\| \| \| \| \|	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.	Carl Worth	2009-11-10
	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.