aboutsummaryrefslogtreecommitdiffhomepage
path: root/notmuch-setup.c
Commit message (Collapse)AuthorAge
* Make exclusion visible againGravatar David Bremner2012-03-03
| | | | | | | | This reverts dfee0f9 man: remove search.exclude_tags from notmuch-config.1 for 0.12 e83409d NEWS: revert NEWS item for exclude tags for 0.12 e77b031 config: disable addition of exclude tags for 0.12
* config: disable addition of exclude tags for 0.12Gravatar Mark Walters2012-03-02
| | | | | This disables the addition of search_exclude_tags in notmuch-setup and notmuch-config.
* setup: prompt user for search.exclude_tags valueGravatar Pieter Praet2012-01-23
| | | | Allow users to customize the search.exclude_tags option during setup.
* setup: Create functions for tag list printing and parsingGravatar Austin Clements2012-01-23
| | | | | | This refactors the tag list printing and parsing currently used for new.tags so that both can be reused for the new search.exclude_tags option.
* notmuch setup: Don't prompt about maildir synchronizationGravatar Carl Worth2010-11-11
| | | | | | | | | | 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.
* Avoid abbreviation, preferring notmuch_config_get_maildir_synchronize_flagsGravatar Carl Worth2010-11-11
| | | | | | | | | | | | | 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).
* Make maildir synchronization configurableGravatar Michal Sojka2010-11-10
| | | | | | | 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.
* notmuch-setup.c: Initialize getline(3) response_size to 0Gravatar Mike Kelly2010-10-29
| | | | | | | This appears to be necessary on FreeBSD. If this isn't done, we get a nasty segfault. See: id:20101013094340.41580a2f@pioto.org
* notmuch: Eliminate some const-correctness warnings.Gravatar Carl Worth2010-10-27
| | | | | | | | 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.
* notmuch setup: Prompt for tags to set on new messages.Gravatar Carl Worth2010-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.Gravatar Carl Worth2009-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.Gravatar Jameson Graef Rollins2009-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_CONFIGGravatar Alec Berryman2009-11-23
| | | | | If present, $NOTMUCH_CONFIG will be used as the configuration file location.
* notmuch new: Unbreak after the addition of notmuch-config.Gravatar Carl Worth2009-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".Gravatar Carl Worth2009-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.Gravatar Carl Worth2009-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.Gravatar Carl Worth2009-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.Gravatar Carl Worth2009-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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-30 02:25:00 +0000