notmuch.git - [no description]

	Commit message (Collapse)	Author	Age
*	config: Rename messages.new_tags to just new.tags	Carl Worth	2010-04-23
\| \| \| \| \| \|	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.
*	Clarify the documentation for the new_tags configuration option.	Carl Worth	2010-04-23
\| \| \| \| \|	Specifically mentioning that it's a list separated by ';' and use "will" instead of "should".
*	notmuch setup: Fix new configuration-file groups to get comments	Carl Worth	2010-04-23
\| \| \| \| \| \| \| \| \| \|	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.
*	Sprinkle some const-correctness around new_tags.	Carl Worth	2010-04-23
\| \| \| \|	To eliminate a compiler warning.
*	notmuch-config: make new message tags configurable	Ben Gamari	2010-04-23
\| \| \| \| \| \|	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.
*	notmuch: Abort if specified configuration file is not found.	Carl Worth	2010-04-21
\| \| \| \| \| \| \| \|	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.
*	* notmuch-config: fix small leak from 'g_key_file_to_data'	Dirk-Jan C. Binnema	2009-12-04
\| \| \| \|	Signed-off-by: Dirk-Jan C. Binnema <djcb.bulk@gmail.com>
*	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-config: Fix memleaks.	Holger Freyther	2009-11-22
\| \| \| \| \| \| \|	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>
*	Deal with situation where sysconf(_SC_GETPW_R_SIZE_MAX) returns -1	Alexander Botero-Lowry	2009-11-17
\|
*	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 setup: Add some comments when creating a .notmuch-config file.	Carl Worth	2009-11-11
\| \| \| \| \|	The "notmuch setup" command is nice and all, but we also want to allow users to conveniently edit the configuration file directly.
*	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.