<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/command-line-arguments.c, branch 0.13_rc1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.13_rc1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.13_rc1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-03-18T12:14:22Z</updated>
<entry>
<title>cli: Parsing. Allow true/false parameter for boolean options.</title>
<updated>2012-03-18T12:14:22Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-03-10T11:05:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b3e4417897f5b27883513c4714f7e84e377b5f5b'/>
<id>urn:sha1:b3e4417897f5b27883513c4714f7e84e377b5f5b</id>
<content type='text'>
Allow NOTMUCH_OPT_BOOLEAN to take a true or false parameter.  In
particular it allows the user to turn off a boolean option with
--option=false.
</content>
</entry>
<entry>
<title>command-line-arguments.[ch]: make arrays of keyword descriptors const</title>
<updated>2011-12-13T04:00:44Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-12-13T03:54:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f717d2ece1836c863f9cc02abd1ff2539307cd1d'/>
<id>urn:sha1:f717d2ece1836c863f9cc02abd1ff2539307cd1d</id>
<content type='text'>
It seems like it should never be necessary to modify these arrays after
initialization.
</content>
</entry>
<entry>
<title>command-line-arguments.[ch]: new argument parsing framework for notmuch.</title>
<updated>2011-12-09T00:24:24Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-12-01T00:27:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2cf7b27a0c4b4e746e2e40752c55ddb4d54798b2'/>
<id>urn:sha1:2cf7b27a0c4b4e746e2e40752c55ddb4d54798b2</id>
<content type='text'>
As we noticed when Jani kindly converted things to getopt_long, much
of the work in argument parsing in notmuch is due to the the key-value
style arguments like --format=(raw|json|text).

The framework here provides positional arguments, simple switches,
and --key=value style arguments that can take a value being an integer,
a string, or one of a set of keywords.
</content>
</entry>
</feed>
