From: Carl Worth <cworth@cworth.org>
To: david@tethera.net, notmuch@notmuchmail.org
Cc: David Bremner <bremner@unb.ca>
Subject: Re: [PATCH 1/2] notmuch-show-get-header: new function; return alist of parsed header fields.
Date: Sat, 20 Feb 2010 12:14:11 -0800 [thread overview]
Message-ID: <87d3zzhdgs.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1265942072-30247-2-git-send-email-david@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On Thu, 11 Feb 2010 22:34:31 -0400, david@tethera.net wrote:
> From: David Bremner <bremner@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, notmuch-show-header-begin-regexp,
> and notmuch-show-message-end-regexp.
Thanks, David.
I've applied this now, (amended to not add any trailing whitespace).
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2010-02-20 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <id:1260021951-3022-1-git-send-email-david@tethera.net>
2010-02-12 2:34 ` Updated notmuch-show-get-* functions david
2010-02-12 2:34 ` [PATCH 1/2] notmuch-show-get-header: new function; return alist of parsed header fields david
2010-02-12 2:34 ` [PATCH 2/2] Add functions notmuch-show-get-(bcc, cc, date, from, subject, to) to 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 david
2010-02-20 20:14 ` Carl Worth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3zzhdgs.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=bremner@unb.ca \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).