From: David Bremner <bremner@debian.org>
To: 687390@bugs.debian.org
Cc: notmuch@notmuchmail.org
Subject: solution to gnus-alias problems?
Date: Sun, 30 Sep 2012 21:57:50 -0300 [thread overview]
Message-ID: <87pq53xb3l.fsf@zancas.localnet> (raw)
Geoff writes:
Hi David,
I've found the source of the problem I was having. It seems to be due
to some interference with the notmuch-mua-reply function and
gnus-alias. In particular, there was a problem with the part of
notmuch-mua-reply that inserted the newly setup message contents.
Towards the end of the notmuch-mua-reply function, there is the following code:
;; insert the message body - but put it in front of the signature
;; if one is present
(goto-char (point-max))
* (if (re-search-backward message-signature-separator nil t)
* (forward-line -1)
(goto-char (point-max)))
(insert body)
(push-mark))
(set-buffer-modified-p nil)
The problem is with the two lines I've marked with a *. Suppose the
main message reply buffer already contains a signature and looks like
this
[Headers]
--text follows this line
--
[Signature text]
The above goes goes to the end of buffer with (point-max), then
searches back to the beginning of the signature separator, which is
fine. But then it moves one line up to the beginning of '--text
follows this line--" and then inserts the newly created message body,
which means that it inserts it before the '--text follows this
line--'.
I've solved the problem (I think) by adjust the above code as follows:
(if (re-search-backward message-signature-separator nil t)
(progn
(beginning-of-line)
(newline))
(goto-char (point-max)))
Hope this helps!
Best,
Geoffrey
next reply other threads:[~2012-10-01 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 0:57 David Bremner [this message]
2012-10-01 15:56 ` solution to gnus-alias problems? Michal Nazarewicz
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=87pq53xb3l.fsf@zancas.localnet \
--to=bremner@debian.org \
--cc=687390@bugs.debian.org \
--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).