aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* emacs: Use truenames for Fcc paths.Gravatar David Edmondson2010-12-07
| | | | | | Appease the test suite by using the true name for the Fcc directory path, otherwise a value for `notmuch-database-path' which includes symbolic links causes test suite failures.
* test: Ignore files created during test failures.Gravatar David Edmondson2010-12-07
| | | | | | | | | When a test fails, a tmp.<testname> file is left behind. These files are useful for the person debugging the test failure, but are never anything we want to commit. Edited-by: Carl Worth <cworth@cworth.org>: Changed from tmp.emacs to tmp.* and added explanation in the commit message.
* notmuch new: Scan directory whenever fs mtime is not equal to db mtimeGravatar Carl Worth2010-12-05
| | | | | | | | | | | | | | Previously, we would only scan a directory if the filesystem modification time was strictly newer than the database modification time for the directory. This would cause a problem for systems with an unstable clock, (if a new mail was added to the filesystem, then the system clock rolled backward, "notmuch new" would not find the message until the clock caught up and the directory was modified again). Now, we always scan the directory if the modification time of the directory is not exactly the same between the filesystem and the database. This avoids the problem described above even with an unstable system clock.
* Fix to index the "Re" term present in any subject.Gravatar Carl Worth2010-11-23
| | | | | | | | | | | This was a misfeature where notmuch had extra code that just threw away legitimate information. It was never indexing an initial "Re" term in a subject. But some users have legitimately wanted to search for this term. The original code was written this way merely for strict compatiblity with the indexing performed by sup, but we're not taking advantage of that now anyway.
* notmuch search: Fix missing final newline in "notmuch search --output=tags"Gravatar Carl Worth2010-11-23
| | | | | | As mentioned in the recent test commits, this also fixes the missing '[' and ']' characters in the --format=json variant of "notmuch search --output=tags" as well.
* test: Add --format=json testing to the "notmuch search --format" tests.Gravatar Carl Worth2010-11-23
| | | | | | | This testing *does* capture the bug of missing '[' and ']' characters int "notmuch search --output=tags" case. This is another manifestation of the same bug causing the missing final newline (as mentioned in the previous commit).
* test: Add simple tests for "notmuch search --output=<>"Gravatar Carl Worth2010-11-23
| | | | | | | | | | | This code simply wasn't being exercised by the test suite before, so this will be useful. Meanwhile, there's currently a bug in "notmuch search --output=tags" in that it doesn't print a final newline. But the current test suite isn't able to catch this bug since the $() construct of the shell doesn't preserve the distinction of whether the final newline is present or not.
* TODO: Note missing keybindings for next/previous thread in emacs client.Gravatar Carl Worth2010-11-23
| | | | Seems a fairly obvious shortcoming to have survived this long.
* compatibility with emacs22Gravatar James Vasile2010-11-16
| | | | | | | | | | Emacs22 lacks apply-partially and mouse-event-p, so define them if emacs version is less than 23. With this change, I was able to begin using notmuch in emacs22. The definitions of apply-partially and mouse-event-p are copied from the emacs 23 distribution, (which is distributed under the GPLv3+ just as notmuch).
* TODO: Add several items recently mentioned on the mailing list.Gravatar Carl Worth2010-11-16
| | | | | Getting things listed here means that I can safely archive away those messages without worrying that the ideas will get lost.
* test: Don't print a test result for preliminary test setupGravatar Carl Worth2010-11-16
| | | | | | | This test script does some initial test setup (generating a few messages), which is all well and good, but we don't need to print that as a test result---particularly since the test result was effectively hard-coded to always pass.
* test: Fix bugs detected thanks to the previous commitGravatar Michal Sojka2010-11-16
|
* test: Detect unfinished subsetsGravatar Michal Sojka2010-11-16
| | | | | | When test_begin_subtest is not followed by corresponding test_expect_equal, the output of the rest of the test script is errornously suppressed. Add code to detect these bugs in test scripts.
* test: Break on test script (or other) errorGravatar Michal Sojka2010-11-16
| | | | | | | | | Break notmuch-test whenever a test script returns non-zero status. This happens either when some test from the script fails or when there is an error in the script. This is especially useful in the latter case since the error may not appear in the final aggregated results.
* test: Add trailing newline to error messagesGravatar Michal Sojka2010-11-16
| | | | | | The newline was removed from say_color in commit 222926ab to allow printing test status in the beginning of the line. Error messages are never followed by other text so we add the newline to error function.
* test: Better handling of stdout and stderrGravatar Michal Sojka2010-11-16
| | | | | | | | | | | | | Git-style tests (test_expect_success etc.) suppress stdout and stderr unless -v is given. Notmuch-style tests (created by test_begin_subtest and test_expect_equal) do not have this behavior so implement it the same. Additionally, for both test styles, the test-lib.sh is changed so that the content of suppressed stdout and stderr is shown in case of failed test. Finally a test for this functionality is added to basic tests.
* emacs: Use `view-mode' when examining raw messages.Gravatar David Edmondson2010-11-16
| | | | | | | Explained-by: Carl Worth: This gives convenient keybindings for navigating the file and for quitting from the buffer, (since, with a raw message file the user will generally want to just view the message, not edit it).
* configure: Add explicit check for glib >= 2.14Gravatar Carl Worth2010-11-16
| | | | For cases where GMime is present, but happy with glib 2.12, for example.
* configure: Use pkg-config --exists rather than --modversionGravatar Carl Worth2010-11-16
| | | | | | | | With --modversion we were asking for output that we were just throwing away anyway. The --exists option does just what we want, (no output and communivating only via return value). Also, --exists allows for testing versions of the package as well.
* lib: Fix missing initialization of status field.Gravatar Carl Worth2010-11-11
| | | | | This could have been a problematic bug. Fortuinately "gcc -O2" warns about it.
* lib: Add two missing static qualifiersGravatar Carl Worth2010-11-11
| | | | | The debian packaging is nice enough to notice when we accidentally leak private symbols to the public interface.
* debian: Update list of symbols for libnotmuchGravatar Carl Worth2010-11-11
| | | | This release adds three new functions to the library interface.
* debian: Add changelog entry for 0.5Gravatar Carl Worth2010-11-11
| | | | Just pulling things from NEWS as usual.
* Increment notmuch version to 0.5Gravatar Carl Worth2010-11-11
| | | | | | | | The big change here is the support for maildir-flag synchronization. But there are a number of other thigns as well---library support for multiple filenames, new ruby bindings, improvements to the vim interface, and a few tweaks to the emacs interface.
* Increment library version to 1.3.0Gravatar Carl Worth2010-11-11
| | | | | | | | For the addition of three functions: notmuch_message_get_filenames notmuch_message_tags_to_maildir_flags notmuch_message_maildir_flags_to_tags
* NEWS: Add notes for 0.5 release.Gravatar Carl Worth2010-11-11
| | | | Which is ready to go now.
* config: Fix confusing of "tag" and "flag" oin documentation.Gravatar Carl Worth2010-11-11
| | | | | It has been very difficult to get all of these right. I would not be surprised if I've still missed some.
* emacs: add stash thread-id function to notmuch-search modeGravatar Jameson Rollins2010-11-11
| | | | | | | | | This add a "stash-map" for search-mode, just like in show-mode, and adds one function, bound to "i" to stash the thread-id of the current selected thread. Couldn't think of the correct way to stash other thread info, so I didn't add any other stash functions for now.
* emacs: mv notmuch-{show,common}-do-stashGravatar Jameson Rollins2010-11-11
| | | | | | | Here we move the notmuch-show/notmuch-show-do-stash function to notmuch-lib/notmuch-common-do-stash. Nothing in this function is notmuch-show mode specific, so this move will make it cleaner to be used by other modes (such as notmuch-search).
* emacs: Improve the definition and use of `notmuch-fcc-dirs'.Gravatar David Edmondson2010-11-11
| | | | | | | | | | | | | | | | | | | | | Re-work the declaration and definition of `notmuch-fcc-dirs'. The variable now allows three types of values: - nil: no Fcc header is added, - a string: the value of `notmuch-fcc-dirs' is the name of the folder to use, - a list: the folder is chosen based on the From address of the current message using a list of regular expressions and corresponding folders: ((\"Sebastian@SSpaeth.de\" . \"privat\") (\"spaetz@sspaeth.de\" . \"OUTBOX.OSS\") (\".*\" . \"defaultinbox\")) If none of the regular expressions match the From address, no Fcc header will be added.
* emacs: Use the header line to show the subject of the thread.Gravatar David Edmondson2010-11-11
|
* emacs: Simplify subjects more aggressively.Gravatar David Edmondson2010-11-11
| | | | | | | | | | | | | | | Remove 're: ' or 'Re: ' from anywhere within a subject line rather than just at the beginning. This is to accommodate threads where a mailing list sometimes inserts a subject prefix. For example, if a thread has the subjects: [Orgmode] org-indent, org-inlinetask: patches on github Re: [Orgmode] org-indent, org-inlinetask: patches on github [Orgmode] Re: org-indent, org-inlinetask: patches on github the last of these would not have been considered the same and would therefore have been shown.
* emacs: Elide the display of repeated subjects in thread display mode.Gravatar David Edmondson2010-11-11
| | | | | Collapsed messages do not show a "Subject:" line if the subject is the same as that of the previous message.
* test: Update emacs tests for fix to counting of signature lines.Gravatar Carl Worth2010-11-11
| | | | The recent bug fix invalidated some expected test results. Fix them up.
* emacs: Correctly count the number of lines in a signature.Gravatar David Edmondson2010-11-11
|
* Update of the spec file to the 0.4 release.Gravatar Scott Henson2010-11-11
|
* tags_to_maildir_flags: Fix to preserve existing, unsupported flagsGravatar Carl Worth2010-11-11
| | | | | | This is to prevent notmuch from destroying any information the user has encoded as flags in the maildir filename. Tests are also added to the test suite to verify the documented behavior.
* notmuch_message_tags_to_maildir_flags: Do nothing outside of "new" and "cur"Gravatar Carl Worth2010-11-11
| | | | | | | | | | | Some people use notmuch with non-maildir files, (for example, email messages in MH format, or else cool things like using sluk[*] to suck down feeds into a format that notmuch can index). To better support uses like that, don't do any renaming for files that are not in a directory named either "new" or "cur". [*] https://github.com/krl/sluk/
* lib: Be honest in the documentation of the maildir functionsGravatar Carl Worth2010-11-11
| | | | | | | | | | I had originally hoped for better semantics, such as doing nothing in non-maildir directories, and preserving unknown maildir flags that happen to be present. We could still do those things, of course, but for now, remove them from the documentation since the implementation does not do these things yet.
* notmuch setup: Fix to add maildir group (with comment) to existing fileGravatar Carl Worth2010-11-11
| | | | | | | The intent of "notmuch setup" is that it adds new, documented sections to configuration files that were created before such sections were defined. But to make this work, we have to explicitly set an option in the maildir group if it didn't exist previously.
* test: Move corpus emails into maildir directory structureGravatar Carl Worth2010-11-11
| | | | | Now that we have maildir synchronization turned on by default, it's advantageous to make all of the tests exercise it as much as possible.
* test: Fix emacs FCC test to account for new maildir synchronizationGravatar Carl Worth2010-11-11
| | | | | | The FCC code saves a message in maildir format, and sets the S flag by default, so now, automatically, FCC messages will not show up as "unread", (which seems natural enough).
* Enable maildir synchronization by default.Gravatar Carl Worth2010-11-11
| | | | | This is a useful feature that most people should want, so enable it by default, (still allowing customization to disable it of course).
* notmuch config: Add more documentation for maildir.synchronize_flagsGravatar Carl Worth2010-11-11
| | | | Including details on which actual flags are synchronized with which tags.
* 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.
* notmuch_message_tags_to_maildir_flags: Don't exit on failure to rename.Gravatar Carl Worth2010-11-11
| | | | | | It is totally legitimate for a non-maildir directory to be named "new" (and not have a directory next to it named "cur"). To support this case at least, be silent about any rename failure.
* test: Drop test for propagating flag changes from one file to anotherGravatar Carl Worth2010-11-11
| | | | | | | | | | | There's nothing in the current API documentation that would suggest the behavior being tested here. Attempt to implement this could have some nasty side effects, (such as notmuch_message_maildir_flags_to_tags implicitly calling notmuch_message_tags_to_maildir_flags and maybe even opening up some bad looping possibilities). Much better to stick with what we have documented, which we believe will actually be useful, (and easy enough to comprehend).
* notmuch_message_tags_to_maildir_flags: Fix to rename multiple filesGravatar Carl Worth2010-11-11
| | | | | This function was documented as modifying every filename associated with the message. Fix it to actually do that.
* notmuch_filenames_create: Take a reference to underlying filename listGravatar Carl Worth2010-11-11
| | | | | The notmuch_filenames_t object might easily outlive the original object owning the filename list. So take a talloc reference to keep things safe.
* maildir_flags_to_tags: Avoid interpreting "no info" as "no flags set".Gravatar Carl Worth2010-11-11
| | | | | | | | | | | | | | | If a filename has no maildir info at all, (that is, it does not contain the sequence ":2,"), we consider this distinct from a filename with an empty maildir info, (the ":2," separator is present, but no flags characters follow). Specifically, we regard a missing info field as providing no information, so tags will remain unchanged. On the other hand, an info field that is present but has no flags set will cause various tags to be cleared, (or in the case of "unread", added). This fixes the "remove info" case of the maildir-sync tests in the test suite.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-29 02:00:14 +0000