From: Chong Yidong <cyd@stupidchicken.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, Tassilo Horn <tassilo@member.fsf.org>,
5175@debbugs.gnu.org
Subject: Re: bug#5175: 23.1.50; mark deactivated without running deactivate-mark-hook when replying with Gnus
Date: Sat, 02 Jan 2010 14:20:26 -0500 [thread overview]
Message-ID: <877hs048lh.fsf@stupidchicken.com> (raw)
In-Reply-To: <b4mbphdmgl7.fsf@jpl.org> (Katsumi Yamaoka's message of "Sat, 02 Jan 2010 10:38:12 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> * message.el (message-exchange-point-and-mark): Call
>> exchange-point-and-mark with an argument rather than setting
>> mark-active by hand (Bug#5175).
>
> This incompatible change makes Gnus not work with old Emacsen, so
> I don't merge it to the Gnus trunk, i.e., No Gnus. Any idea not
> to use the argument of `exchange-point-and-mark'?
I've reworked the change to use the simpler functions from my previous
message; I think this should solve the backward compatibility problem.
next prev parent reply other threads:[~2010-01-02 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87aaxqdf9z.fsf@thinkpad.tsdh.de>
2010-01-02 1:38 ` Katsumi Yamaoka
2010-01-02 2:41 ` Chong Yidong
2010-01-02 19:20 ` Chong Yidong [this message]
2010-01-05 2:23 ` 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=877hs048lh.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=5175@debbugs.gnu.org \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.org \
--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.
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).