Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Leo <sdl.web@gmail.com>, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: compose-mail-other-window
Date: Mon, 28 May 2007 12:06:15 +0900	[thread overview]
Message-ID: <b4mveedabpz.fsf@jpl.org> (raw)
In-Reply-To: <87wsytekd0.fsf@stupidchicken.com>

>>>>> In <87wsytekd0.fsf@stupidchicken.com> Chong Yidong wrote:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> 2007-03-15  Katsumi Yamaoka  <yamaoka@jpl.org>
>>
>> 	* message.el (message-generate-new-buffers):
>> [...]
>> 	(message-mail): Prefer `switch-function' if it is given;
>>
>> It requires running `message-mode' further.  I've fixed it in
>> both the trunk and the v5-10 branch of the Gnus CVS repository.
>> I think this change is worth merging to not only the Emacs trunk
>> but also the EMACS_22_BASE branch.

> I checked it, and it looks good.  I checked it into the EMACS_22_BASE
> branch.  Thanks.

> (I assumed the automagic syncing between Gnus CVS and Emacs CVS HEAD
> will take care of the trunk; is that right?)

Thank you very much for this.  Could you merge another fix that
I made recently to the EMACS_22_BASE branch, too?   The discussion
is here:

http://news.gmane.org/group/gmane.emacs.gnus.general/thread=64667/force_load=t

And this is the patch:

2007-05-24  Katsumi Yamaoka  <yamaoka@jpl.org>

	* message.el (message-narrow-to-headers-or-head): Ignore
	mail-header-separator in the body.

--8<---------------cut here---------------start------------->8---
*** message.el~	Mon May 28 03:03:46 2007
--- message.el	Mon May 28 03:05:06 2007
***************
*** 2225,2238 ****
    (widen)
    (narrow-to-region
     (goto-char (point-min))
!    (cond
!     ((re-search-forward
!       (concat "^" (regexp-quote mail-header-separator) "\n") nil t)
!      (match-beginning 0))
!     ((search-forward "\n\n" nil t)
!      (1- (point)))
!     (t
!      (point-max))))
    (goto-char (point-min)))
  
  (defun message-news-p ()
--- 2225,2236 ----
    (widen)
    (narrow-to-region
     (goto-char (point-min))
!    (if (re-search-forward (concat "\\(\n\\)\n\\|^\\("
! 				  (regexp-quote mail-header-separator)
! 				  "\n\\)")
! 			  nil t)
!        (or (match-end 1) (match-beginning 2))
!      (point-max)))
    (goto-char (point-min)))
  
  (defun message-news-p ()
--8<---------------cut here---------------end--------------->8---

Thanks in advance.

  reply	other threads:[~2007-05-28  3:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <460570D5.4010307@gmx.at>
     [not found] ` <m2abvsfmtd.fsf@sl392.st-edmunds.cam.ac.uk>
2007-05-28  2:13   ` compose-mail-other-window Katsumi Yamaoka
2007-05-28  2:46     ` compose-mail-other-window Chong Yidong
2007-05-28  3:06       ` Katsumi Yamaoka [this message]
2007-05-28  4:13         ` compose-mail-other-window Chong Yidong
2007-05-28  4:18           ` compose-mail-other-window Katsumi Yamaoka
2007-05-29  0:03       ` compose-mail-other-window Richard Stallman
2007-05-28  7:25     ` compose-mail-other-window Leo
2007-05-29  0:03     ` compose-mail-other-window Richard Stallman
2007-05-29  0:22       ` compose-mail-other-window Katsumi Yamaoka

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4mveedabpz.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=cyd@stupidchicken.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@gmail.com \
    /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.
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 NNTP newsgroup(s).