Gnus development mailing list
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: "Gabor Z. Papp" <gzp@papp.hu>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Top posting related changes in the cvs
Date: Wed, 04 Apr 2007 01:02:17 +0200	[thread overview]
Message-ID: <87ps6ljc3q.fsf@ambire.localdomain> (raw)
In-Reply-To: <v9slbhnmfq.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed\, 04 Apr 2007 00\:05\:29 +0200")

() Reiner Steib <reinersteib+gmane@imap.cc>
() Wed, 04 Apr 2007 00:05:29 +0200

   I gather that you refer to an interactive call of
   `message-yank-original' (C-c C-y) after doing a reply/followup
   without citing the original (using `r'/`f').

yes.
                                         
   However, when using `R'/`F', I don't get this behavior anymore:
   Point is _below_ the quote, which is wrong.

patch below seems to fix `R'/`F' w/ light testing.
here is a ChangeLog entry:

        * gnus-msg.el (gnus-inews-yank-articles):
        Fix bug: Make sure point is at eob after yanking.

probably all callers of `message-yank-original' should be checked.
does that give good results?

thi



*** gnus-msg.el	31 Mar 2007 09:43:42 -0000	1.38
--- gnus-msg.el	3 Apr 2007 22:57:22 -0000
***************
*** 771,776 ****
--- 771,777 ----
  		 (nnheader-narrow-to-headers)
  		 (nnheader-parse-naked-head)))))
  	(message-yank-original)
+ 	(exchange-point-and-mark)       ; point to eob
  	(setq beg (or beg (mark t))))
        (when articles
  	(insert "\n")))

  reply	other threads:[~2007-04-03 23:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 17:29 Gabor Z. Papp
2007-04-03 20:45 ` Reiner Steib
2007-04-03 21:38   ` Thien-Thi Nguyen
2007-04-03 22:05     ` Reiner Steib
2007-04-03 23:02       ` Thien-Thi Nguyen [this message]
2007-04-03 23:11         ` Gabor Z. Papp
2007-04-09  6:40         ` Katsumi Yamaoka
2007-04-09 18:30           ` Thien-Thi Nguyen
2007-04-09 19:49           ` Reiner Steib
2007-04-09 23:15             ` Katsumi Yamaoka
2007-04-03 21:10 ` Graham Murray

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=87ps6ljc3q.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=gzp@papp.hu \
    /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).