aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
...
* python: remove Tags().__len__() implementationGravatar Sebastian Spaeth2011-08-09
| | | | | | | | | | | len() exhausts the tag iterator and e.g. list() or "".join(tags) implicitly call len() if existing and then failing. So, we remove Tags.__len__(). If you need to know the number of tags a message has, do use len(list(tags)). It would be nicer to be able to support len() directly... Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* python: Do explicitly check if the next tag existsGravatar Sebastian Spaeth2011-08-09
| | | | | | | | If we try to pull a non-existing tag, Tags._get will return None and the appended .decode() command will fail. So make sure that there is a tag to be fetched before fetching it. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* python: pep8 compliance for __init__.pyGravatar pazz2011-08-09
|
* python: pep8 compliance for thread.pyGravatar pazz2011-08-09
|
* python: pep8 compliance for tag.pyGravatar pazz2011-08-09
|
* python: pep8 compliance for globals.pyGravatar pazz2011-08-09
|
* python: pep8 compliance for filename.pyGravatar pazz2011-08-09
|
* python: pep8 compliance for database.pyGravatar pazz2011-08-09
|
* python: pep8 compliance for message.pyGravatar pazz2011-08-09
|
* python: Really throw an error if search_threads() failsGravatar Sebastian Spaeth2011-08-09
| | | | | | | | | | | | In case, search_threads returns an error we are supposed to throw an Exception. But we did not "raise" it, this was an oversight and this commit fixes it. There is still the problem that there is often output to stderr by libnotmuch detailing the xapian error and this is simply printed out. But this requires fixing at the libnotmuch level... Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* python: Fix copy'n paste typoGravatar Cedric Cabessa2011-08-09
| | | | | | | we accessed a wrong attribute due to a copy and paste error. Thanks for catching this. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* Merge branch 'release'Gravatar David Bremner2011-08-01
|\
| * debian: new changelog stanza for 0.7Gravatar David Bremner2011-08-01
| | | | | | | | | | No actual changes, but we need a new stanza to upload to unstable anyway.
| * update NEWS for 0.7Gravatar David Bremner2011-08-01
| | | | | | | | Essentially point form from git log --oneline.
| * version: bump to 0.7Gravatar David Bremner2011-08-01
| | | | | | | | No actual changes since 0.7~rc1
| * Revert "debian: Generate version from debian/changelog"Gravatar David Bremner2011-07-29
| | | | | | | | | | | | | | | | This reverts commit 2b76283b52a2389a591ca055b086381c44e2a61f. Conflicts: debian/rules
| * build-system: Add pre-release targetGravatar David Bremner2011-07-29
| | | | | | | | | | | | | | This is a lighter weight version of the release target, intended to support uploading release candidates to Debian. As a side effect, filter ~ out of VERSION to make tag names.
| * bump upstream version to 0.7~rc1Gravatar David Bremner2011-07-29
| |
| * debian: changelog stanza for release candiateGravatar David Bremner2011-07-29
| |
* | ruby: Fix typo in documentationGravatar Ali Polatel2011-07-29
| | | | | | | | It's Notmuch::FileNames not Notmuch::Filenames
* | ruby: Remove the split file hack from rdoc.shGravatar Ali Polatel2011-07-29
| |
* | ruby: Add markers to method definitions to help rdocGravatar Ali Polatel2011-07-29
| | | | | | | | | | rdoc is dumb and needs markers in method definitions so that she can find which source file the method is defined in
* | ruby: Document remaining undocumented constantsGravatar Ali Polatel2011-07-29
| |
* | ruby: Document constants and exceptions right before definitionGravatar Ali Polatel2011-07-29
| |
* | 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>