From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: "Gabor Z. Papp" <gzp@papp.hu>, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Top posting related changes in the cvs
Date: Mon, 09 Apr 2007 20:30:33 +0200 [thread overview]
Message-ID: <873b39bdti.fsf@ambire.localdomain> (raw)
In-Reply-To: <b4mmz1iyrrr.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon\, 09 Apr 2007 15\:40\:40 +0900")
() Katsumi Yamaoka <yamaoka@jpl.org>
() Mon, 09 Apr 2007 15:40:40 +0900
Anyway, I verified that, before this change, there has already
been the problem that happens when `message-yank-original' is
called interactively. So, I'm not a culprit. ;-)
my bad. i apologize for the mis-analysis. i guess the point is
that it was a long-standing discrepency masked by a long-standing
discrepency workaround.
> * gnus-msg.el (gnus-inews-yank-articles):
> Fix bug: Make sure point is at eob after yanking.
I think the recent change in `message-yank-original' and this
fix are the right solutions for Gnus v5.11. However, for No
Gnus, it doesn't solve the problem in the case where
`message-cite-reply-above' is non-nil and `message-yank-original'
is called interactively. How about this one?
* message.el (message-yank-original):
Don't exchange point and mark.
I also removed the `(unless (< (point) (mark-marker)) ...)' test
since I think it will never return nil.
i have no opinion on No Gnus, just on the Gnus distributed w/ Emacs
(that i can play around with (and break, apparently)).
thi
next prev parent reply other threads:[~2007-04-09 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x6lkh9xt79@gzp>
2007-04-03 20:45 ` Top posting related changes in the cvs 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
2007-04-03 23:11 ` Gabor Z. Papp
2007-04-09 6:40 ` Katsumi Yamaoka
2007-04-09 18:30 ` Thien-Thi Nguyen [this message]
2007-04-09 19:49 ` Reiner Steib
2007-04-09 23:15 ` 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=873b39bdti.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=gzp@papp.hu \
--cc=yamaoka@jpl.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.