aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* ruby: Add list of classes to main documentationGravatar Ali Polatel2011-07-29
|
* libnotmuch: only build symbols list after the modules are builtGravatar Thomas Jost2011-07-20
| | | | | | If the notmuch.sym target does not explicitly depend on $(libnotmuch_modules), gen-version-script.sh may be run before all the .o files are created, for example when doing a parallel build on a machine with many cores.
* Merge commit '0.6.1'Gravatar David Bremner2011-07-17
|\ | | | | | | | | | | | | | | | | | | | | | | Conflicts: lib/Makefile.local The conflicts are from three kinds of commits not merged into release: - typo fixes - removal of debug output - fix for CLEAN rule That were never merged into the release branch.
| * build-system: tag debian-version as part of the release targetGravatar David Bremner2011-07-17
| | | | | | | | | | | | This allows, e.g. gitpkg debian/0.x-1 to do the right thing. It also helps enforce the convention that Debian upload -1 is identical to the release tarball.
| * debian: use 3.0 (quilt) source format.Gravatar David Bremner2011-07-17
| | | | | | | | | | | | | | | | | | This generates a seperate notmuch-0.x.debian.tar.gz containing ./debian. In the initial release this is redundant, but for Debian only updates between releases, this allows updating the contents of ./debian, and using the rest of the release tarball.
| * build-system: update version check to support non-native packages.Gravatar David Bremner2011-07-17
| | | | | | | | | | We could be a bit more flexible about this and support optional Debian versions, but for the moment, we pick a policy and stick to it.
| * build-system: guard parts irrevokable parts of release target with REALLY_UPLOADGravatar David Bremner2011-07-17
| | | | | | | | | | | | | | This supports both testing and use by non-upload privileged users. Along with previous commits in the series, this lets one do a dry run of the release process and created a tarball, signature file, and release announcement to inspect before uploading.
| * build-system: use signed tag to make tar file, if available.Gravatar David Bremner2011-07-17
| | | | | | | | | | This as the advantage that "make VERSION=n.m dist" will work correctly even if the wrong branch happens to be checked out.
| * build-system: tag earlier in the release process.Gravatar David Bremner2011-07-17
| | | | | | | | If tagging fails, we really don't want to upload tarballs.
| * build-system: remove use of git-buildpackage, dput. Add pristine-tar.Gravatar David Bremner2011-07-17
| | | | | | | | | | | | | | | | | | | | | | | | The previous setup was dependent on the git-buildpackage configuration to find the resulting tar file, and consequently a bit fragile. We use pristine-tar instead to save a checksum-identical copy of the tar file. This will also faciliate "non-native" debian packages, if desired. dput again depends on the local configuration, and mainly is a bit too brave for me to do automatically.
| * build-system: run make clean before testing.Gravatar David Bremner2011-07-17
| | | | | | | | | | | | The reasoning is that we might have some error in the build system that causes something not to be rebuilt; this would potentially have the tests run on the wrong version of the code.
| * build-system: replace use of ssh with wget for checking the websiteGravatar David Bremner2011-07-17
| | | | | | | | | | | | | | The idea is to see if the version we are already releasing exists on the notmuch website. Using wget allows more people to run this target, and also allows people with ssh access to run it without access to their keys.
| * version: bump to 0.6.1Gravatar David Bremner2011-07-17
| |
| * update NEWS and debian/changelog for 0.6.1Gravatar David Bremner2011-07-17
| |
| * debian: use a non-native version number.Gravatar David Bremner2011-07-17
| | | | | | | | | | | | | | | | | | There is concensus to use non-native version number for updates that contain only Debian changes. Unfortunately changing back and forth between native and non-native packages has the potential for confusion, since the archive will end up with notmuch-0.x.tar.gz and notmuch-0.x.orig.tar.gz. So we use non-native numbering from the beginning.
| * debian: add (demangled) Xapian exception typeinfo symbols to libnotmuch1.symbolsGravatar David Bremner2011-07-16
| | | | | | | | | | These are exported (again) by the library to prevent problems with catching exceptions.
| * libnotmuch: export Xapian typeinfo symbolsGravatar David Bremner2011-07-16
| | | | | | | | | | | | | | | | | | | | | | The lack of such exporting seems to cause problems catching exceptions, as suggested by http://gcc.gnu.org/wiki/Visibility This manifested in the symbol-hiding test failing when notmuch was compile with gcc 4.4.5. On i386, this further manifested as notmuch new failing to run (crashing with an uncaught exception on first run).
* | vim: fix citation/signature fold lengthsGravatar Jason Woofenden2011-07-16
| | | | | | | | | | | | Before they'd often miss the last line Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | vim: fix (hack) cig/cit parsing within multipart/*Gravatar Jason Woofenden2011-07-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The vim front-end isn't written to handle nested parts. This patch doesn't change that, it just changes the code to pretend that multipart/* sections end immediately. This makes the parsing code think that all sections are top-level, and are thus parsed well enough. The lovely result of this is that citation folds and signature folds now work in text/plain parts that are within multipart/* sections. Also, all mime section starts are now shown correctly (before some were not parsed and showed the ugly ^L and an ID and so on from notmuch.) Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | vim: fix on-screen instructions for show-signatureGravatar Jason Woofenden2011-07-16
| | | | | | | | | | | | | | Also change a passed parameter to be consistent with the current binding. This parameter appears to be unused. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | vim: fix from list reformatting in search viewGravatar Jason Woofenden2011-07-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch rewrites the reformatting of the from list so it shows full capitalized names when available (without truncating them as the old code did) and removes the pipe characters that appear between some names. The old code appears to assume from list (the list of senders in the thread) coming from notmuch would be e-mail addresses, but in this version it is mostly full names. Also in this version, the names are sometimes separated by pipe instead of comma. For consistency with old versions, names are still truncated at the first period. Perhaps they shouldn't be though. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | vim: fix space key: now archives (did opposite)Gravatar Jason Woofenden2011-07-16
| | | | | | | | | | | | | | | | | | In vim, in the message view, space is supposed to remove the "unread" and "inbox" tags, but was sometimes adding them instead. This patch assures that they are always removed by this binding. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | vim: use the full path for sendmailGravatar Uwe Kleine-König2011-07-16
| | | | | | | | | | | | ... as /usr/sbin isn't usually in user's PATH. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | vim: skip trailing slash for g:notmuch_compose_temp_file_dirGravatar Uwe Kleine-König2011-07-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the trailing slash I get Error detected while processing function <SNR>10_NM_new_mail..<SNR>10_NM_cmd_compose..<SNR>10_NM_newComposeBuffer..<SNR>10_NM_newFileBuffer: line 3: E739: Cannot create directory: /home/ukleinek/.notmuch/compose/ when hitting 'm' to compose a new mail. strace shows: stat("/home/ukleinek/.notmuch/compose/", 0x7fffee314a10) = -1 ENOENT (No such file or directory) stat("/home/ukleinek/.notmuch/compose/", 0x7fffee314e30) = -1 ENOENT (No such file or directory) stat("/home/ukleinek/.notmuch/compose", 0x7fffee315270) = -1 ENOENT (No such file or directory) stat("/home/ukleinek/.notmuch", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 mkdir("/home/ukleinek/.notmuch/compose", 0755) = 0 mkdir("/home/ukleinek/.notmuch/compose/", 0755) = -1 EEXIST (File exists) so it seems vim's mkdir() isn't able to handle a trailing slash. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | vim: fix documentation that mailx isn't used anymoreGravatar Uwe Kleine-König2011-07-16
| | | | | | | | | | | | | | | | Since e7899b0 (vim: use sendmail directly) notmuch-vim uses sendmail directly. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
* | python: represent message tags as unicode instancesGravatar Sebastian Spaeth2011-07-11
| | | | | | | | | | | | | | | | | | | | | | | | Rather than returning simply strings and having to guess their encoding, return explicit unicode() strings for the tags. Xapian stores UTF8, so we know that they come as UTF8 encoded string. Note: I tried to directly use the c_wchar_p type of the ctypes library which translates directly into an unicode type, but that did not work out so well, so we take c_char_p and .decode() them manually. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* | python: Encode query string as a utf-8 byte arrayGravatar Sebastian Spaeth2011-07-11
| | | | | | | | | | | | | | | | | | If we pass in an unicode instance as query string, we would probably get weird behavior (and indeed do so, see mail id:"20110707113700.GA16347@megatron"). If a unicode instance is passed in, make sure we encode it properly to an utf-8 encoded byte string. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* | Merge commit '0.6'Gravatar David Bremner2011-07-10
|\ \
| | * debian: update changelog for strict libnotmuch dependencyGravatar David Bremner2011-07-10
| | |
| | * debian: strictly depend on the same version of libnotmuchGravatar Uwe Kleine-König2011-07-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It took quite some time to debug why folder: searches didn't work for me though I had notmuch 0.6~rc1 installed. amdragon in #notmuch found out that I still had libnotmuch1 0.5+nmu3 installed. To prevent the same problem in the future let notmuch depend on the same version of libnotmuch1. Reviewed-By: David Bremner <david@tethera.net> The underlying issue is that the libnotmuch interface is not entirely captured by the set of exported symbols. In particular the query syntax can change without being visible to the linker at all.
* | | python: Fix Database().needs_upgrade()Gravatar Sebastian Spaeth2011-07-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | A stupid typo was preventing this from ever working and it was not detected until now. Patrick noted the typo and proposed the fix in mail id:"20110704203926.GA20238@brick.lan". Patch-by: Patrick Totzke <patricktotzke@googlemail.com> Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
| | * debian: start new changelog stanza for post 0.6 bugfix releaseGravatar David Bremner2011-07-07
| | | | | | | | | | | | | | | | | | The version numbering scheme of n.n.n is chosen so as not to confuse tools that rely on the presence of a dash to detect non-native packages.
| | * debian: install README.Debian files for notmuch-vim and notmuch-emacs.Gravatar David Bremner2011-07-07
| |/ | | | | | | | | The notmuch-vim README.Debian in particular is quite important since it discussions the need to install the package with vim-addons
* | Use POSIX sed invocationGravatar Robin Green2011-07-03
| | | | | | | | | | | | Fixes broken build on DragonFly BSD Signed-off-by: Robin Green <greenrd@greenrd.org>
* | version: bump to 0.6Gravatar David Bremner2011-07-01
| | | | | | | | | | | | The release machinery in the build system depends on this file being correct. (cherry picked from commit 6bd02fb4dbee9e0fc372661af573a2ac380fed8a)
* | NEWS: Update for release 0.6Gravatar David Bremner2011-07-01
| | | | | | | | | | | | | | | | | | | | | | Fix some typos, add some notes on python bindings, "improve" the folder searching description, expand the discussion of crypto changes. This includes the changes from id:"1309541202-4938-1-git-send-email-dmitry.kurochkin@gmail.com" Thanks to Sebastian, Austin, and Uwe, Dmitry for the editing help. (cherry picked from commit 74d00bb0e847a1aa785b9cae2e8242a7789bf8b3)
* | debian: add changelog stanza for release 0.6, install upstream docs referred to.Gravatar David Bremner2011-07-01
| | | | | | | | | | | | This perhaps breaks the "one thing at a time rule", but seems better than leaving the changelog pointing to nothing. (cherry picked from commit 8c5129bb510b9f4f7acc9752cc61a457eceb6f01)
| * version: bump to 0.6Gravatar David Bremner2011-07-01
| | | | | | | | | | The release machinery in the build system depends on this file being correct.
| * NEWS: Update for release 0.6Gravatar David Bremner2011-07-01
| | | | | | | | | | | | | | | | | | | | Fix some typos, add some notes on python bindings, "improve" the folder searching description, expand the discussion of crypto changes. This includes the changes from id:"1309541202-4938-1-git-send-email-dmitry.kurochkin@gmail.com" Thanks to Sebastian, Austin, and Uwe, Dmitry for the editing help.
| * debian: add changelog stanza for release 0.6, install upstream docs referred to.Gravatar David Bremner2011-07-01
| | | | | | | | | | This perhaps breaks the "one thing at a time rule", but seems better than leaving the changelog pointing to nothing.
| * debian: move vim directory creation to notmuch-vim binary packageGravatar David Bremner2011-07-01
| | | | | | | | | | | | | | | | | | This step was missed during the package split of notmuch to notmuch, notmuch-emacs, and notmuch-vim. It seems mostly harmless in this case, but it is silly for non-vim users to have those directories. (cherry picked from commit 4b5875d81ef80dd7138e178f59ac67f66d5fe0ab)
| * NEWS: Add notes for (imminent) notmuch 0.6 releaseGravatar Carl Worth2011-07-01
| | | | | | | | | | | | By skimming through "git log 0.5..origin/release" late at night. Hopefully everything here is accurate. (cherry picked from commit d173069ad9cf042458f16af00729867cb13bb3b7)
| * emacs: Fix to unconditionally display subject changes in collapsed thread viewGravatar Carl Worth2011-07-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The feature to show subject changes in the collapsed thread view was originally added (8ab433607) with an option (notmuch-show-always-show-subject) to display the subject for all messages, even when there was no change. The subsequent commit (4f04d273) changed the sense of the test (or to and) and the name of the controlling variable (notmuch-show-elide-same-subject). But this commit is broken in a few ways: 1. The original definition of notmuch-show-always-show-subject was left around But the variable isn't actually used in the code at all, so it just adds clutter and confusion to the customization interface. 2. The name and description of the controlling variable doesn't match the implementation The name suggests that setting the variable to t will cause repeated subjects to be elided, (suggesting that when it is nil all subjects will be shown). However, when the variable is nil, no subjects are shown. So a correct name for the variable in this sense would be notmuch-show-subject-changes. Showing subject changes is a useful feature, and should be on by default. (We don't want to bury generally useful features behind customizations that users have to find). Rather than fixing the name of the variable and changing its default value, here we remove the condition entirely, such that the feature is enabled unconditionally. So both the currently-used variable and the stale definition of the formerly-used are removed. Also, the one relevant test-suite result is updated, (showing the intial subject of a collapsed thread, and no subject display for later messages that do not change the subject). (cherry picked from commit 580de27177de5cd6c5cbc9cc3759ce320216dd5b)
* | debian: move vim directory creation to notmuch-vim binary packageGravatar David Bremner2011-07-01
| | | | | | | | | | | | | | | | This step was missed during the package split of notmuch to notmuch, notmuch-emacs, and notmuch-vim. It seems mostly harmless in this case, but it is silly for non-vim users to have those directories.
* | NEWS: Add notes for (imminent) notmuch 0.6 releaseGravatar Carl Worth2011-07-01
| | | | | | | | | | By skimming through "git log 0.5..origin/release" late at night. Hopefully everything here is accurate.
* | emacs: Fix to unconditionally display subject changes in collapsed thread viewGravatar Carl Worth2011-07-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The feature to show subject changes in the collapsed thread view was originally added (8ab433607) with an option (notmuch-show-always-show-subject) to display the subject for all messages, even when there was no change. The subsequent commit (4f04d273) changed the sense of the test (or to and) and the name of the controlling variable (notmuch-show-elide-same-subject). But this commit is broken in a few ways: 1. The original definition of notmuch-show-always-show-subject was left around But the variable isn't actually used in the code at all, so it just adds clutter and confusion to the customization interface. 2. The name and description of the controlling variable doesn't match the implementation The name suggests that setting the variable to t will cause repeated subjects to be elided, (suggesting that when it is nil all subjects will be shown). However, when the variable is nil, no subjects are shown. So a correct name for the variable in this sense would be notmuch-show-subject-changes. Showing subject changes is a useful feature, and should be on by default. (We don't want to bury generally useful features behind customizations that users have to find). Rather than fixing the name of the variable and changing its default value, here we remove the condition entirely, such that the feature is enabled unconditionally. So both the currently-used variable and the stale definition of the formerly-used are removed. Also, the one relevant test-suite result is updated, (showing the intial subject of a collapsed thread, and no subject display for later messages that do not change the subject).
| * debian: changelog stanza for first "official" release candidateGravatar David Bremner2011-06-30
| | | | | | | | | | | | | | The last upload to experimental was really a release candidate too. Switch versioning to ~rc1 as counting commits is confusing when building from the release branch. (cherry picked from commit 117852a5f1269e77a7f76c53236220a9ec89eba6)
* | debian: changelog stanza for first "official" release candidateGravatar David Bremner2011-06-30
| | | | | | | | | | | | The last upload to experimental was really a release candidate too. Switch versioning to ~rc1 as counting commits is confusing when building from the release branch.
| * debian: don't install zsh completion files into /usr/share/zshGravatar David Bremner2011-06-30
| | | | | | | | | | | | | | | | | | | | | | | | as of version 4.3.12, perhaps earlier, the Debian zsh package now ships /usr/share/zsh/functions/Completion/Unix/_notmuch, so we shouldn't install that ourselves anymore. My understanding is that letting zsh ship the completion scripts is the standard thing to do. The script is still shipped in /usr/share/doc/notmuch/examples (cherry picked from commit 0a0f5f1bbe4bf256a14dee0ab2af3065a251a72c)
* | debian: don't install zsh completion files into /usr/share/zshGravatar David Bremner2011-06-30
| | | | | | | | | | | | | | | | | | | | | | as of version 4.3.12, perhaps earlier, the Debian zsh package now ships /usr/share/zsh/functions/Completion/Unix/_notmuch, so we shouldn't install that ourselves anymore. My understanding is that letting zsh ship the completion scripts is the standard thing to do. The script is still shipped in /usr/share/doc/notmuch/examples
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-23 02:52:26 +0000