>On Thu, 11 Feb 2010 15:20:54 +0100 (CET), racin at free.fr wrote:
>
>> Using a prefix arg to invert search order would conflict with my patch
>> http://notmuchmail.org/pipermail/notmuch/2009/000914.html in which the
>> prefix arg is used to show deleted messages. I don't known which
>> behaviour
From: David Bremner
Provide key bindings for stuffing various RFC822 header fields and other
metadata
into the emacs kill-ring as text. The bindings are as follows:
z F notmuch-show-stash-filename
z T notmuch-show-stash-tags
z c
From: David Bremner
The previous version would crash when a key was bound to a sparse
keymap, since apparently these are not straightforward lists. The
usage of map-keymap is a bit obscure: it only has side-effects, no
return value.
---
notmuch.el |8 ++--
1 files
These patches let you header fields and similar into the emacs kill-ring
(and the X11 clipboard/selection, if things are setup right).
Patch 1/2 is actually a bug fix to master, unchanged since last time.
The bug didn't manifest because no submaps were used.
Patch 2/2 is rebased against current
notmuch-show-stash-to
Great new emacs UI feature. Love it.
jamie.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100211/dde98171/attachment.pgp>
On Thu, 11 Feb 2010 22:11:46 +0530, "Aneesh Kumar K.V" wrote:
> From: Aneesh Kumar K.V
>
> This patch helps in customizing search result display
> similar to mutt's index_format. The customization is done
> by defining an alist as below
>
> (setq notmuch-search-result-format '(("date" . "%s ")
From: David Bremner
Return the corresponding header field for the current message as a
string. These are thin wrappers around notmuch-show-get-header, which
means they each cause a full parse of the RFC822 header. The main idea
is to fix an api.
---
Sorry, resending with fixed
From: David Bremner
---
notmuch.el | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index c96fd94..d2a3b1b 100644
--- a/notmuch.el
+++ b/notmuch.el
@@ -225,6 +225,38 @@ Unlike builtin `previous-line'
From: David Bremner
This function parses the displayed message to recover header
fields. It uses mailheader.el to do the actual header parsing, after
preprocessing to remove indentation. It relies on the variables
notmuch-show-message-begin-regexp,
I have rebased the patch for notmuch-show-get-header,and added functions
for each of the header fields (I think) parsed by mailheader.el.
There is a corresponding updated stash patch series that uses these functions
to provide
convenient access to various fields, even if not currently
From: Aneesh Kumar K.V
This patch helps in customizing search result display
similar to mutt's index_format. The customization is done
by defining an alist as below
(setq notmuch-search-result-format '(("date" . "%s ")
("authors" .
Using a prefix arg to invert search order would conflict with my patch
http://notmuchmail.org/pipermail/notmuch/2009/000914.html
in which the prefix arg is used to show deleted messages. I don't known which
behaviour for prefix patch would be best.
Though we can also add "toggle keys" that
On Thu, 11 Feb 2010 14:01:14 +, David Edmondson wrote:
> (let ((proc (start-process-shell-command
>"notmuch-search" buffer notmuch-command "search"
>(if oldest-first "--sort=oldest-first"
> "--sort=newest-first")
Doh, I should shut up when I
I've had enough of the
On a sunny Sunday the 30th in timezone , male human with mail
address hit the reply button microseconds after 1970 while being at
latitude :
type of reply template in notmuch. :-)
May I suggest to use a simpler:
"On 11 Feb 2010, David Edmondson wrote:"
(using
On Thu, 11 Feb 2010 12:19:12 +, David Edmondson wrote:
...
I think the correct thing here would be to let notmuch return search is
inverse sort order rather than reverting this later in the client
(unneccessary work).
--sort=oldest|newest|relevance
seems to be what xapian can easily
On Thu, 11 Feb 2010 14:42:40 +0100, "Sebastian Spaeth" wrote:
> On Thu, 11 Feb 2010 12:19:12 +, David Edmondson wrote:
> ...
>
> I think the correct thing here would be to let notmuch return search is
> inverse sort order rather than reverting this later in the client
> (unneccessary work).
: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100211/4bed5de7/attachment.pgp>
c: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100211/e57c9cc7/attachment.pgp>
---
notmuch.el |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index 8f50abe..de9ddf8 100644
--- a/notmuch.el
+++ b/notmuch.el
@@ -1398,7 +1398,8 @@ characters as well as `_.+-'.
(defun notmuch-search (query oldest-first)
"Run \"notmuch
---
notmuch.el |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index 040997e..8f50abe 100644
--- a/notmuch.el
+++ b/notmuch.el
@@ -1104,6 +1104,7 @@ matching this search term are shown if non-nil. "
(define-key map "-"
also sprach Sebastian Spaeth [2010.02.10.2225 +1300]:
> "notmuch dump tag:notmuch and tag:patch" could be used to construct a
> list of "accepted", "willnottakeit","superseded" and "pending" lists or
> whatever. If that list were made accessible somewhere, this would be
> super useful. At least
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: broken-mail-in-notmuch-emacs
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100211/18d14330/attachment.txt>
also sprach David Bremner [2010.02.10.2149 +1300]:
> I'm not sure what merging patches means here; some kind of squash
> operation? Anyway it seemed to me that every every patch series
> that I looked at was broken into individual patches. Maybe I am
> just unlucky, or does patchwork really not
> PS. I know that attaching the output of "git format-patch" to a message
> like this isn't the "git way". (That is, you won't get the right result
> by simply piping this message to "git am".) But I really wish it
> were. It seems I often write code in response to an email message and I
> often
On Wed, 10 Feb 2010 12:54:52 -0800, Carl Worth wrote:
> PS. I know that attaching the output of "git format-patch" to a message
> like this isn't the "git way". (That is, you won't get the right result
> by simply piping this message to "git am".) But I really wish it
> were. It seems I often
PS. I know that attaching the output of git format-patch to a message
like this isn't the git way. (That is, you won't get the right result
by simply piping this message to git am.) But I really wish it
were. It seems I often write code in response to an email message and I
often want to
Hi,
recently, I got a message (attached) which is diplayed incorrectly in
emacs GUI. Instead of the message I see direct output of notmuch show
(with ^L characters). I wonder whether it is a porblem of notmuch or it
is because the message does not comform to standards. What do you think?
Michal
---
notmuch.el |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index 040997e..8f50abe 100644
--- a/notmuch.el
+++ b/notmuch.el
@@ -1104,6 +1104,7 @@ matching this search term are shown if non-nil.
(define-key map - 'notmuch-search-remove-tag)
---
notmuch.el |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index 8f50abe..de9ddf8 100644
--- a/notmuch.el
+++ b/notmuch.el
@@ -1398,7 +1398,8 @@ characters as well as `_.+-'.
(defun notmuch-search (query optional oldest-first)
Run
On Thu, 11 Feb 2010 12:19:12 +, David Edmondson d...@dme.org wrote:
...
I think the correct thing here would be to let notmuch return search is
inverse sort order rather than reverting this later in the client
(unneccessary work).
--sort=oldest|newest|relevance
seems to be what xapian
I've had enough of the
On a sunny Sunday the 30th in timezone wurgs, male human X with mail
address z hit the reply button bar microseconds after 1970 while being at
latitude foo:
type of reply template in notmuch. :-)
May I suggest to use a simpler:
On 11 Feb 2010, David Edmondson wrote:
On Thu, 11 Feb 2010 14:01:14 +, David Edmondson d...@dme.org wrote:
(let ((proc (start-process-shell-command
notmuch-search buffer notmuch-command search
(if oldest-first --sort=oldest-first
--sort=newest-first)
Doh, I should shut up when I
Using a prefix arg to invert search order would conflict with my patch
http://notmuchmail.org/pipermail/notmuch/2009/000914.html
in which the prefix arg is used to show deleted messages. I don't known which
behaviour for prefix patch would be best.
Though we can also add toggle keys that toggle
On Thu, 11 Feb 2010 15:20:54 +0100 (CET), ra...@free.fr wrote:
Using a prefix arg to invert search order would conflict with my patch
http://notmuchmail.org/pipermail/notmuch/2009/000914.html in which the
prefix arg is used to show deleted messages. I don't known which
behaviour for prefix
Hi Michal,
I found myself today *really* needing to add a test that exercises some
code in our emacs client. (Eric found that a message that includes a :
in the From: address breaks things due to a buggy regexp.) And I
wanted to see if I could merge your conversion of the test suite before
I
also sprach Sebastian Spaeth sebast...@sspaeth.de [2010.02.12.0254 +1300]:
I've had enough of the
On a sunny Sunday the 30th in timezone wurgs, male human X with mail
address z hit the reply button bar microseconds after 1970 while being
at latitude foo:
type of reply template in
From: David Bremner brem...@unb.ca
This function parses the displayed message to recover header
fields. It uses mailheader.el to do the actual header parsing, after
preprocessing to remove indentation. It relies on the variables
notmuch-show-message-begin-regexp,
From: David Bremner brem...@unb.ca
---
notmuch.el | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/notmuch.el b/notmuch.el
index c96fd94..d2a3b1b 100644
--- a/notmuch.el
+++ b/notmuch.el
@@ -225,6 +225,38 @@ Unlike builtin `previous-line'
From: David Bremner brem...@unb.ca
Return the corresponding header field for the current message as a
string. These are thin wrappers around notmuch-show-get-header, which
means they each cause a full parse of the RFC822 header. The main idea
is to fix an api.
---
Sorry, resending with fixed
These patches let you header fields and similar into the emacs kill-ring
(and the X11 clipboard/selection, if things are setup right).
Patch 1/2 is actually a bug fix to master, unchanged since last time.
The bug didn't manifest because no submaps were used.
Patch 2/2 is rebased against current
From: David Bremner brem...@unb.ca
The previous version would crash when a key was bound to a sparse
keymap, since apparently these are not straightforward lists. The
usage of map-keymap is a bit obscure: it only has side-effects, no
return value.
---
notmuch.el |8 ++--
1 files
On Thu, 11 Feb 2010 23:01:08 -0400, da...@tethera.net wrote:
From: David Bremner brem...@unb.ca
Provide key bindings for stuffing various RFC822 header fields and other
metadata
into the emacs kill-ring as text. The bindings are as follows:
z F notmuch-show-stash-filename
z T
42 matches
Mail list logo