aboutsummaryrefslogtreecommitdiffhomepage
path: root/notmuch.c
Commit message (Collapse)AuthorAge
...
* notmuch.c: Shorten version stringGravatar Sebastian Spaeth2010-04-16
| | | | | | | | We previously output "notmuch version 0.1" as response to notmuch --version. Shorten this to "notmuch 0.1" as we know that we will receive a version number when we explicitely ask for it. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* notmuch count: Remove unneeded paragraph from documentation.Gravatar Carl Worth2010-04-09
| | | | | This paragraph acts like it's introducing an example, but then no example is given. Just drop this.
* notmuch count: Remove special handling of "*".Gravatar Carl Worth2010-04-09
| | | | | | From both the implementation and from the documentation. This is handled generically in the library for all search-based commands, so count doesn't need special treatment.
* notmuch: Document the new special-case syntax of "*".Gravatar Carl Worth2010-04-09
| | | | This functionality came through a recent addition to the library.
* Have notmuch count default to showing the total.Gravatar Mike Kelly2010-04-09
| | | | | | | If no parameters are given to notmuch-count, or just '' or '*' are given, return the total number of messages in the database. update notmuch count help
* Merge remote branch 'dme/dme-for-cworth'Gravatar Carl Worth2010-04-02
|\ | | | | | | | | Conflicts: notmuch.c (Simply the change in documentation indentation level).
* | notmuch help: Eliminate a gratuitous level of indentation.Gravatar Carl Worth2010-04-02
| | | | | | | | | | | | I don't really know why we ended up having everything indented by two tabs, (perhaps trying to make it match the man page)? But wihout any containing context to justify that it just looks odd.
* | notmuch help: Simplify output by omitting arguments for each command.Gravatar Carl Worth2010-04-02
| | | | | | | | | | | | | | | | | | The output was far too busy otherwise. It's more useful to just show the argument list in the case of "notmuch help <command>" for a specific command. (Credit due to running "git help" and seeing a much more readable list than what was coming out of "notmuch help".)
* | notmuch: Add a version (0.1 initially) with a new --version option.Gravatar Carl Worth2010-04-02
| | | | | | | | | | We're planning to do actual releases soon, so we need a version number to put into the tar file.
* | notmuch: Add support for a --help option.Gravatar Carl Worth2010-04-02
| | | | | | | | | | | | Previously, only "notmuch help" worked while a call to "notmuch --help" would just print a message telling the user to call "notmuch help". Instead of the redirection, just support --help directly now.
| * notmuch: Add a 'part' subcommandGravatar David Edmondson2010-04-02
|/ | | | | | | | | | | A new 'part' subcommand allows the user to extract a single part from a MIME message. Usage: notmuch part --part=<n> <search terms> The search terms must match only a single message (e.g. id:foo@bar.com). The part number specified refers to the part identifiers output by `notmuch show'. The content of the part is written the stdout with no formatting or identification marks. It is not JSON formatted.
* Add is:<tag> as a synonym for tag:<tag> in search terms.Gravatar Carl Worth2010-03-09
| | | | | I like the readability of this, it provides compatibility with people trained in this syntax by sup, and it even saves one character.
* Add an "--format=(json|text)" command-line option to both notmuch-search and ↵Gravatar Scott Robinson2010-02-23
| | | | | | | | | | | | | notmuch-show. In the case of notmuch-show, "--format=json" also implies "--entire-thread" as the thread structure is implicit in the emitted document tree. As a coincidence to the implementation, multipart message ID numbers are now incremented with each part printed. This changes the previous semantics, which were unclear and not necessary related to the actual ordering of the message parts.
* notmuch new: Remove hack to ignore read-only directories in mail store.Gravatar Carl Worth2010-01-06
| | | | | | | This was really the last thing keeping the initial run of "notmuch new" being different from all other runs. And I'm taking a fresh look at the performance of "notmuch new" anyway, so I think we can safely drop this optimization.
* notmuch.1: Document the new --entire-thread option to "notmuch show".Gravatar Carl Worth2009-12-02
| | | | | This was added to "notmuch help" earlier, but not to the man page. Add it there, and use consistent wording in both places.
* notmuch show: limit display to only matching messagesGravatar Bart Trojanowski2009-12-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch changes the default behaviour of notmuch show to display only messages that match the search expression. However, --entire-thread option is provided to display all messages in threads that matched the search expression. It is deemed that will be more useful for human users on the command line. Scripts can be modified to include the --entire-thread option so that they can display all messages once more. Example: $ notmuch search subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b thread:23d99d0f364f93e90e15df8b42eddb5b July 31 [4/12] Johan Herland; [RFCv2 00/12] Foreign VCS helper program for CVS repositories (inbox unread) Note that in this thread 4 out of 12 messages matched. The default show behaviour is to show only those messages that match: $ notmuch show subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b | grep 'message{' | wc -l 4 With the --entire-thread option the output will contain all dozen messages: $ notmuch show --entire-thread subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b | grep 'message{' | wc -l 12 Signed-off-by: Bart Trojanowski <bart@jukie.net>
* Documentation for notmuch reply --format=(default|headers-only)Gravatar Jed Brown2009-11-28
| | | | Signed-off-by: Jed Brown <jed@59A2.org>
* search-tags: Add support for search-terms.Gravatar Jan Janak2009-11-26
| | | | | | | | | | | | | | | This patch adds support for search-terms to 'notmuch search-tags'. If no search-term is provided then the command returns a list of all tags from the database. If the user provides one or more search-terms as arguments then the command collects tags from matching messages only. This could be used by functions in the Emacs mode to further limit the list of tags offered for completion. For example, functions that remove tags from message(s) could offer only tags present in the message(s). Signed-off-by: Jan Janak <jan@ryngle.com>
* notmuch: New command 'search-tags'.Gravatar Jan Janak2009-11-26
| | | | | | | | | | This is a new notmuch command that can be used to search for all tags found in the database. The resulting list is alphabetically sorted. The primary use-case for this new command is to provide the tag completion feature in Emacs (and other interfaces). Signed-off-by: Jan Janak <jan@ryngle.com>
* notmuch search: Remove the chunked-searching hack.Gravatar Carl Worth2009-11-23
| | | | | | | | | | | | | This was a poor workaround around the fact that the existing notmuch_threads_t object is implemented poorly. It's got a fine iterartor-based interface, but the implementation does all of the work up-front in _create rather than doing the work incrementally while iterating. So to start fixing this, first get rid of all the hacks we had working around this. This drops the --first and --max-threads options from the search command, (but hopefully nobody was using them anyway---notmuch.el certainly wasn't).
* Fix printing of literal '%' in help message.Gravatar Carl Worth2009-11-23
| | | | I suppose I could have just used puts instead...
* Add rudimentary date-based search.Gravatar Carl Worth2009-11-23
| | | | | | | | | | | | | The rudimentary aspect here is that the date ranges are specified with UNIX timestamp values (number of seconds since 1970-01-01 UTC). One thing that can help here is using the date program to determins timestamps, such as: $(date +%s -d 2009-10-01)..$(date +%s) Long-term, we'll probably need to do our own query parsing to be able to support directly-specified dates and also relative expressions like "since:'2 months ago'".
* Add 'notmuch count' command to show the count of matching messagesGravatar Keith Packard2009-11-23
| | | | | | | | | | | Getting the count of matching threads or messages is a fairly expensive operation. Xapian provides a very efficient mechanism that returns an approximate value, so use that for this new command. This returns the number of matching messages, not threads, as that is cheap to compute. Signed-off-by: Keith Packard <keithp@keithp.com>
* Support multiple configuration files via $NOTMUCH_CONFIGGravatar Alec Berryman2009-11-23
| | | | | If present, $NOTMUCH_CONFIG will be used as the configuration file location.
* Support for printing file paths in new commandGravatar Adrian Perez2009-11-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | For very large mail boxes, it is desirable to know which files are being processed e.g. when a crash occurs to know which one was the cause. Also, it may be interesting to have a better idea of how the operation is progressing when processing mailboxes with big messages. This patch adds support for printing messages as they are processed by "notmuch new": * The "new" command now supports a "--verbose" flag. * When running in verbose mode, the file path of the message about to be processed is printed in the following format: current/total: /path/to/message/file Where "current" is the number of messages processed so far and "total" is the total count of files to be processed. The status line is erased using an ANSI sequence "\033[K" (erase current line from the cursor to the end of line) each time it is refreshed. This should not pose a problem because nearly every terminal supports it. * The signal handler for SIGALRM and the timer are not enabled when running in verbose mode, because we are already printing progress with each file, periodical reports are not neccessary.
* notmuch main(): Remove stale comment.Gravatar Carl Worth2009-11-18
| | | | The code this comment was referring to has since been deleted.
* notmuch help: Print to stdout, not to stderr.Gravatar Lars Kellogg-Stedman2009-11-18
| | | | | | Let usage() take a FILE * argument so that you can output to stderr in response to usage errors, and stdout in response to an explicit request.
* notmuch help: Update documentation (following recent text from notmuch.1)Gravatar Carl Worth2009-11-17
| | | | | | | We take the recently created text from the notmuch manual page and update the "notmuch help" command to use similar text. In particular, we add a new "notmuch help search-terms" for documenting the search syntax that is common to several commands.
* 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: Make the command of "notmuch" walk the user through the next step.Gravatar Carl Worth2009-11-11
| | | | | | | | If this is run first, it will run "notmuch setup" directly. After that is successful, it will look for a databae and tell the user to run "notmuch new" if the database doesn't exist yet. Finally, if the database is present, it will provide some example "notmuch search" commands for the user to try.
* 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 reply: Use GMime to construct the header for the reply.Gravatar Carl Worth2009-11-11
| | | | | | | | | The advantage here is that we actually get the necessary folding of long headers, (particularly the References header, but also things like Subject). This also gives us parsed recipient addresses so that we can easily elide the sender's address(es) from the recipient list (just as soon as we have a configured value for the recipient's address(es)).
* notmuch reply: Add (incomplete) reply commandGravatar Keith Packard2009-11-10
| | | | | | | | | | | | | | Reviewed-by: Carl Worth <cworth@cworth.org> Keith wrote all the code here against notmuch before notmuch.c was split up into multiple files. So I've pushed the code around in various ways to match the new code structure, but have generally tried to avoid making any changes to the behavior of the code. I did fix one bug---a missing call to g_mime_stream_file_set_owner in show_part which would cause "notmuch show" to go off into the weeds when trying to show multiple messages, (since the first stream would fclose stdout).
* 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.
* notmuch setup: Remove a debugging print.Gravatar Carl Worth2009-11-09
| | | | | This was just some extra noise printed when requesting a non-default mail directory itneractively.
* notmuch show: Don't show the subject line twice.Gravatar Carl Worth2009-11-06
| | | | | | | | I recently added a print of the subject line for use as part of a two-line summary in the emacs client. But of course, the subject was already being printed on the next line. So I didn't really need to add anything, I could have just stopped hiding what was already printed. Anyway, we now avoid printing it twice in a row.
* notmuch show: Move subject from one-line summary down to its own line.Gravatar Carl Worth2009-11-05
| | | | | And change the display code in emacs to display the one-line summary in inverse video.
* Update notmuch man page with recently-added documentation.Gravatar Carl Worth2009-11-05
| | | | | It would be nice to have this documentation live in a single place, but for now, this is what we get.
* notmuch search: Document the from, to, and subject prefixes.Gravatar Carl Worth2009-11-05
| | | | | I've been using these for a long time, but I had neglected to document them until now.
* notmuch show: Fix to work with any search string rather than just a thread ID.Gravatar Carl Worth2009-11-05
| | | | | | | | | | | The more general command is more consistent, and more useful. We also fix "notmuch search" to output copy-and-pasteable search terms for the thread with "thread:" prepended already. Similarly, the message-ID in the output of "notmuch show" is also now printed as a valid search term, ("id:<message-id>" rather than "ID: <message-id>"). Naturally, the emacs code is also changed to track these changes.
* notmuch show: Add filename to output (next to message ID).Gravatar Carl Worth2009-11-04
| | | | | This will allow a client using "notmuch show" to directly open the filename and do whatever it wants with it.
* notmuch show: Fix misplaced g_object_unref leading to error message.Gravatar Carl Worth2009-11-04
| | | | | | | | | | We were inadvertently calling g_object_unref on a wild pointer leading to the following error message: GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Now, why glib doesn't abort on critical errors, I'll never understand.
* notmuch show: Remove custom "unread" hack, (printing tag in two locations).Gravatar Carl Worth2009-11-03
| | | | | | | | I previously had a hack that special-cased the "unread" tag and printed it on the same line as the message ID. But now that we are printing all tags at the end of the one-line summary we don't need this anymore. Get rid of it, and just read "unread" from the list of tags just like any other tag.
* notmuch show: Print tags for each message.Gravatar Carl Worth2009-11-03
| | | | | This is in the one-line summary so should always be visible even in our emacs client that's so eager to make things invisible.
* Hide bodies of message that have already been read.Gravatar Carl Worth2009-11-03
| | | | | | | | | | | | Also hide all markers. From here, all we really need for legibility is the following: * Hide away citations and signatures * Call out the one-line summary some way, (larger font size?) * Add nesting for replies
* notmuch show: Switch to control character to mark sections of outputGravatar Carl Worth2009-11-02
| | | | | | | | | | We were previously using things like "%message{" which were not guaranteed to never appear in an email message. Using a control character (^L or '\f' instead of '%') gives us better assurance that our delimiter doesn't show up in an original email message. This still isn't entirely safe since we're decoding encoded text in the body of the email message so almost all bets are off really.
* Tweak relative dates to be close to the same length.Gravatar Carl Worth2009-11-02
| | | | | Most all of the returned strings will now fill most of a 12-character string, (depending on the length of the month).
* notmuch show: Don't print non-text MIME parts.Gravatar Carl Worth2009-11-02
| | | | | | Additionally, print a part number for each MIME part so that the client could (conceivably) ask for the contents of a specific part by part number.
* Print "part" markers for each MIME part (with Content-type).Gravatar Carl Worth2009-11-02
| | | | | This can allow for the client to hide undesired MIME parts such as text/html.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-03 11:10:19 +0000