Emacs Keybindings no longer work after upgrading to 0.17
Hi,
I have this function:
(define-key notmuch-search-mode-map "a"
(lambda ()
"Archive message."
(interactive)
(notmuch-search-tag "-inbox")
(notmuch-search-tag "-lowpriority")
(notmuch-search-tag "- at review")
(notmuch-search-tag "- at respond")
))
With the upgrade, if I try pressing "a" in search view, I get:
Wrong type argument: stringp, 43
Yet if I run the commands manually, it works fine.
The full error, BTW, is:
Debugger entered--Lisp error: (wrong-type-argument stringp 45)
string-match("^[-+]\\S-+$" 45 nil)
#[(tag-change) "\305\306\307\310\n#,?\205\311\312!\207" [tag-change start
string regexp inhibit-changing-match-data "^[-+]\\S-+$" nil t string-match
error "Tag must be of the form `+this_tag' or `-that_tag'"] 4](45)
mapc(#[(tag-change) "\305\306\307\310\n #,?\205\311\312!\207"
[tag-change start string regexp inhibit-changing-match-data "^[-+]\\S-+$" nil t
string-match error "Tag must be of the form `+this_tag' or `-that_tag'"] 4]
"-inbox")
notmuch-tag("(id:20140414235421.43aad8ffb333 at www.pentaxforums.com)"
"-inbox")
notmuch-search-tag("-inbox")
(lambda nil "Archive message." (interactive) (notmuch-search-tag "-inbox")
(notmuch-search-tag "-lowpriority") (notmuch-search-tag "- at review")
(notmuch-search-tag "- at respond"))()
call-interactively((lambda nil "Delete message." (interactive)
(notmuch-search-tag "-inbox") (notmuch-search-tag "-lowpriority")
(notmuch-search-tag "- at review") (notmuch-search-tag "- at respond")) nil nil)
Strangely enough, the following works in show view.
(define-key notmuch-show-mode-map "a"
(lambda ()
"Archive message."
(interactive)
(notmuch-show-tag-message "-inbox")
(notmuch-show-tag-message "-lowpriority")
(notmuch-show-tag-message "- at review")
(notmuch-show-tag-message "- at respond")
))
--
Dictionaries are for loosers.
/\ /\ /\ /
/ \/ \ u e e n / \/ a w a z
>>mueen at nawaz.org<<
anl
[PATCH] nmbug: mark repository as bare on clone
"W. Trevor King" writes: > Still, these are just quibbles with the commit message. I'm +1 on the > code change. My initial bare-resistance [2] was because I didn't > realize that an explicit GIT_WORK_TREE would override the core.bare > setting. OK, pushed with an amended commit message/ d
[PATCH v2] NEWS: Document the recent 'nmbug clone' and @{upstream} changes
The changes landed with c200167 (nmbug: Add 'clone' and replace
FETCH_HEAD with @{upstream}, 2014-03-09).
The preferred markup language for NEWS seems to be Markdown, which is
parsed by devel/news2wiki.pl into Markdown chunks for rendering by
ikiwiki [1].
[1]: http://notmuchmail.org/news/
---
Changes since v1 [1]:
* Use HTTP (instead of the Git protocol) for the remote URL [2].
* Remove ?bare? from the text motivating a fresh clone.
Replace it with a reference to remote-tracking branches [2,3].
* Elaborate on the local-commit-backup step (step 1) [4].
[1]: id:151b4a1b9612daa53fb47b60f0aa65f7a8e5ef5e.1396972599.git.wking at
tremily.us
http://thread.gmane.org/gmane.mail.notmuch.general/17457/focus=17812
[2]: id:20140409210108.GB21805 at odin.tremily.us
http://article.gmane.org/gmane.mail.notmuch.general/17817
[3]: id:87bnw2wcwq.fsf at zancas.localnet
http://article.gmane.org/gmane.mail.notmuch.general/17885
[4]: id:20140410020559.GC21805 at odin.tremily.us
http://article.gmane.org/gmane.mail.notmuch.general/17819
NEWS | 22 ++
1 file changed, 22 insertions(+)
diff --git a/NEWS b/NEWS
index d4f4ea4..630607f 100644
--- a/NEWS
+++ b/NEWS
@@ -20,6 +20,28 @@ Bug fix for saved searches with newlines in them.
Split lines confuse `notmuch count --batch`, so we remove embedded
newlines before calling notmuch count.
+nmbug
+-
+
+nmbug adds a `clone` command for setting up the initial repository and
+uses `@{upstream}` instead of `FETCH_HEAD` to track upstream changes.
+
+ The `@{upstream}` change reduces ambiguity when fetching multiple
+ branches, but requires existing users update their `NMBGIT`
+ repository (usually `~/.nmbug`) to distinguish between local and
+ remote-tracking branches. The easiest way to do this is:
+
+ 1. If you have any purely local commits (i.e. they aren't in the
+ nmbug repository on nmbug.tethera.net), push them to a remote
+ repository. We'll restore them from the backup in step 4.
+ 2. Remove your `NMBGIT` repository (e.g. `mv .nmbug .nmbug.bak`).
+ 3. Use the new `clone` command to create a fresh clone:
+
+nmbug clone http://nmbug.tethera.net/git/nmbug-tags.git
+
+ 4. If you had local commits in step 1, add a remote for that
+ repository and fetch them into the new repository.
+
Notmuch 0.17 (2013-12-30)
=
--
1.9.1.353.gc66d89d
[PATCH] nmbug: mark repository as bare on clone
On Sat, Apr 12, 2014 at 01:30:32PM -0300, David Bremner wrote:
> As far as I can figure out, if a git repository is non-bare, then it
> should either have core.worktree set, or the parent directory should
> be the worktree.
If this works in your testing, then +1 from me ;). However, the
default is the current working directory, not the repo's parent
directory [1]:
core.worktree
?
If --git-dir or GIT_DIR is specified but none of --work-tree,
GIT_WORK_TREE and core.worktree is specified, the current working
directory is regarded as the top level of your working tree.
> % cd $HOME && ln -s .nmbug .git && git reset --hard
>
> would delete a bunch of files.
Actually, that would just clobber existing ~/tags/{message-id}/{tag}
files, which the user likely doesn't have. To remove files, you'd
need something like:
$ cd $HOME && ln -s .nmbug .git && git clean -f
Still, these are just quibbles with the commit message. I'm +1 on the
code change. My initial bare-resistance [2] was because I didn't
realize that an explicit GIT_WORK_TREE would override the core.bare
setting.
Cheers,
Trevor
[1]: https://www.kernel.org/pub/software/scm/git/docs/git-config.html
[2]: http://article.gmane.org/gmane.mail.notmuch.general/17817
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20140415/a1fa4d2e/attachment.pgp>
[PATCH] emacs: remove auto-signing of replies to signed messages
On Tue, Apr 15 2014, David Bremner wrote: > Jameson Graef Rollins writes: > >> It was decided that auto-signing is potentially too troublesome for the >> apparently common case of users who enable crypto processing for the >> purpose of checking signature validity but who are not in a position to >> sign out-going messages. Users can still manually invoke signing as needed. > > pushed Awesome. Thank you Jani and David for fixing this issue. jamie. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 818 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20140415/3cdb7d96/attachment.pgp>
[PATCH v2 1/2] emacs: hello: bugfix: make alphabetically sorted saved searches work
Mark Walters writes: > My recent changes to the saved search format broke the alphabetically > sorted saved sort option. This makes it work again. > > Also update docs for saved-search sort defcustom to match the new > format. series pushed d
[PATCH] emacs: remove auto-signing of replies to signed messages
Jameson Graef Rollins writes: > It was decided that auto-signing is potentially too troublesome for the > apparently common case of users who enable crypto processing for the > purpose of checking signature validity but who are not in a position to > sign out-going messages. Users can still manually invoke signing as needed. pushed d
Re: [PATCH] emacs: remove auto-signing of replies to signed messages
Jameson Graef Rollins jroll...@finestructure.net writes: It was decided that auto-signing is potentially too troublesome for the apparently common case of users who enable crypto processing for the purpose of checking signature validity but who are not in a position to sign out-going messages. Users can still manually invoke signing as needed. pushed d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH v2 1/2] emacs: hello: bugfix: make alphabetically sorted saved searches work
Mark Walters markwalters1...@gmail.com writes: My recent changes to the saved search format broke the alphabetically sorted saved sort option. This makes it work again. Also update docs for saved-search sort defcustom to match the new format. series pushed d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] emacs: remove auto-signing of replies to signed messages
On Tue, Apr 15 2014, David Bremner da...@tethera.net wrote: Jameson Graef Rollins jroll...@finestructure.net writes: It was decided that auto-signing is potentially too troublesome for the apparently common case of users who enable crypto processing for the purpose of checking signature validity but who are not in a position to sign out-going messages. Users can still manually invoke signing as needed. pushed Awesome. Thank you Jani and David for fixing this issue. jamie. pgpT2pkPrVjBE.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] nmbug: mark repository as bare on clone
On Sat, Apr 12, 2014 at 01:30:32PM -0300, David Bremner wrote:
As far as I can figure out, if a git repository is non-bare, then it
should either have core.worktree set, or the parent directory should
be the worktree.
If this works in your testing, then +1 from me ;). However, the
default is the current working directory, not the repo's parent
directory [1]:
core.worktree
…
If --git-dir or GIT_DIR is specified but none of --work-tree,
GIT_WORK_TREE and core.worktree is specified, the current working
directory is regarded as the top level of your working tree.
% cd $HOME ln -s .nmbug .git git reset --hard
would delete a bunch of files.
Actually, that would just clobber existing ~/tags/{message-id}/{tag}
files, which the user likely doesn't have. To remove files, you'd
need something like:
$ cd $HOME ln -s .nmbug .git git clean -f
Still, these are just quibbles with the commit message. I'm +1 on the
code change. My initial bare-resistance [2] was because I didn't
realize that an explicit GIT_WORK_TREE would override the core.bare
setting.
Cheers,
Trevor
[1]: https://www.kernel.org/pub/software/scm/git/docs/git-config.html
[2]: http://article.gmane.org/gmane.mail.notmuch.general/17817
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Re: Synchronization success stories?
David Mazieres dm-list-email-notm...@scs.stanford.edu writes: David Bremner da...@tethera.net writes: Brian Sniffen bsnif...@akamai.com writes: I'm thrilled by using notmuch to manage my mail. Low-latency search is very important to me. But I use computers in a couple of places---several of which are laptops. Has anyone stories to share of successful multi-computer notmuch sync, for a corpus of a quarter-million messages or so? I use syncmaildir to sync the actual messages, and a copy of the output of notmuch dump in git to sync the metadata. It works OK. A bit slow; depends how often you need to fetch new mail. If you want to see my solution, it is here: http://www.scs.stanford.edu/~dm/muchsync-0.tar.gz Thanks! Much sync. Wow. It sounds like you're paying very careful attention to correctness and performance, so I'm very glad to be able to start from that basis. -Brian I'm a little embarrassed by this code, as I just started to test it a week ago then instantly became completely dependent on it. I will probably change the name (from muchsync to syncmuch) and the database format before releasing. But if you feel like beta-testing and giving me feedback, have a look. Beware that if you have been using notmuch dump, you may become instantly hooked on my solution... David -- Brian Sniffen Information Security Akamai Technologies ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: Synchronization success stories?
David Bremner da...@tethera.net writes: With a reused ssh connection this is sufficiently fast for me (2s). If there is interest I can clean up the script of hardcoded paths etc. and put it on github. Sure, sounds at least as good as what I am using. Also, syncmaildir recently did something pretty annoying for upward compatibility, so in the long term I'm interested in alternatives. I've put the ruby script with a README on github: https://github.com/til/notmuch-rsync Til pgpZ41nxhzQwK.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Emacs Keybindings no longer work after upgrading to 0.17
Hi, I have this function: (define-key notmuch-search-mode-map a (lambda () Archive message. (interactive) (notmuch-search-tag -inbox) (notmuch-search-tag -lowpriority) (notmuch-search-tag -@review) (notmuch-search-tag -@respond) )) With the upgrade, if I try pressing a in search view, I get: Wrong type argument: stringp, 43 Yet if I run the commands manually, it works fine. The full error, BTW, is: Debugger entered--Lisp error: (wrong-type-argument stringp 45) string-match(^[-+]\\S-+$ 45 nil) #[(tag-change) \305\306\307\310\n#,?\205\311\312!\207 [tag-change start string regexp inhibit-changing-match-data ^[-+]\\S-+$ nil t string-match error Tag must be of the form `+this_tag' or `-that_tag'] 4](45) mapc(#[(tag-change) \305\306\307\310\n #,?\205\311\312!\207 [tag-change start string regexp inhibit-changing-match-data ^[-+]\\S-+$ nil t string-match error Tag must be of the form `+this_tag' or `-that_tag'] 4] -inbox) notmuch-tag((id:20140414235421.43aad8ffb...@www.pentaxforums.com) -inbox) notmuch-search-tag(-inbox) (lambda nil Archive message. (interactive) (notmuch-search-tag -inbox) (notmuch-search-tag -lowpriority) (notmuch-search-tag -@review) (notmuch-search-tag -@respond))() call-interactively((lambda nil Delete message. (interactive) (notmuch-search-tag -inbox) (notmuch-search-tag -lowpriority) (notmuch-search-tag -@review) (notmuch-search-tag -@respond)) nil nil) Strangely enough, the following works in show view. (define-key notmuch-show-mode-map a (lambda () Archive message. (interactive) (notmuch-show-tag-message -inbox) (notmuch-show-tag-message -lowpriority) (notmuch-show-tag-message -@review) (notmuch-show-tag-message -@respond) )) -- Dictionaries are for loosers. /\ /\ /\ / / \/ \ u e e n / \/ a w a z mu...@nawaz.org anl ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
