<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-setup.c, branch 0.11_rc2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.11_rc2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.11_rc2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-11-11T11:53:14Z</updated>
<entry>
<title>notmuch setup: Don't prompt about maildir synchronization</title>
<updated>2010-11-11T11:53:14Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-11-11T11:53:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ebe733632dbd048dae7cabb3b40e9f4d8326a8c9'/>
<id>urn:sha1:ebe733632dbd048dae7cabb3b40e9f4d8326a8c9</id>
<content type='text'>
This synchronization is one of those features that should just happen
automatically. We allow for customization in case someone *really*
wants to turn it off, but we don't need to prompt for this
interactively.

People with special needs can find the configuration file on their
own.
</content>
</entry>
<entry>
<title>Avoid abbreviation, preferring notmuch_config_get_maildir_synchronize_flags</title>
<updated>2010-11-11T11:40:19Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-11-11T00:26:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4cfb2a02778bac16e785bbea1fd6c665e34bd955'/>
<id>urn:sha1:4cfb2a02778bac16e785bbea1fd6c665e34bd955</id>
<content type='text'>
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).
</content>
</entry>
<entry>
<title>Make maildir synchronization configurable</title>
<updated>2010-11-10T21:09:32Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2010-10-31T21:29:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d9d3d3e6f06a76dc0fbe24c9655b64acfcd4b9e4'/>
<id>urn:sha1:d9d3d3e6f06a76dc0fbe24c9655b64acfcd4b9e4</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>notmuch-setup.c: Initialize getline(3) response_size to 0</title>
<updated>2010-10-29T20:13:02Z</updated>
<author>
<name>Mike Kelly</name>
<email>pioto@pioto.org</email>
</author>
<published>2010-10-14T18:18:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=14f1a79f44fde886c8c3f4c7cbcf17daf8fb34e2'/>
<id>urn:sha1:14f1a79f44fde886c8c3f4c7cbcf17daf8fb34e2</id>
<content type='text'>
This appears to be necessary on FreeBSD. If this isn't done, we get a
nasty segfault.

See: id:20101013094340.41580a2f@pioto.org
</content>
</entry>
<entry>
<title>notmuch: Eliminate some const-correctness warnings.</title>
<updated>2010-10-28T01:07:37Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-28T01:07:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c6e70e15eaf7355fb9fe9b599aef07f2be619968'/>
<id>urn:sha1:c6e70e15eaf7355fb9fe9b599aef07f2be619968</id>
<content type='text'>
These were introduced as a side-effect of commit
b9eac48c22f53f84ed1d9c1d8ca862a7b638c9ac (shame on me for doing
side-effect commits like that!).

For me, at least, compilation is now warning-free.
</content>
</entry>
<entry>
<title>notmuch setup: Prompt for tags to set on new messages.</title>
<updated>2010-04-23T17:30:40Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-23T17:30:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=14fb9f3c5531f45c9b5bf2e710f033288bcda5c8'/>
<id>urn:sha1:14fb9f3c5531f45c9b5bf2e710f033288bcda5c8</id>
<content type='text'>
Our "notmuch setup" command is only really helpful if it guides the
user through all the possible options. So add this one.
</content>
</entry>
<entry>
<title>notmuch setup: Exit if EOF is encountered at any prompt.</title>
<updated>2009-12-01T16:06:09Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-12-01T16:06:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=eb0cf86c7a9d5cda464d4d36a9cac66f26b5529d'/>
<id>urn:sha1:eb0cf86c7a9d5cda464d4d36a9cac66f26b5529d</id>
<content type='text'>
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().
</content>
</entry>
<entry>
<title>modify notmuch_setup_command to return 1 if config file write fails.</title>
<updated>2009-11-26T03:24:27Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2009-11-22T21:58:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=34c840a23e1db4c6cf4a836b441d027fc17e9706'/>
<id>urn:sha1:34c840a23e1db4c6cf4a836b441d027fc17e9706</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Support multiple configuration files via $NOTMUCH_CONFIG</title>
<updated>2009-11-23T02:01:57Z</updated>
<author>
<name>Alec Berryman</name>
<email>alec@thened.net</email>
</author>
<published>2009-11-22T05:18:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=91d1d3f043b82d5f3f8c04f2db71a829a7406131'/>
<id>urn:sha1:91d1d3f043b82d5f3f8c04f2db71a829a7406131</id>
<content type='text'>
If present, $NOTMUCH_CONFIG will be used as the configuration file
location.
</content>
</entry>
<entry>
<title>notmuch new: Unbreak after the addition of notmuch-config.</title>
<updated>2009-11-12T03:50:15Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-12T03:50:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=37bdd8987094220c84ec39f8f550753219f68bd4'/>
<id>urn:sha1:37bdd8987094220c84ec39f8f550753219f68bd4</id>
<content type='text'>
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).
</content>
</entry>
</feed>
