From: Chong Yidong <cyd@stupidchicken.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Tassilo Horn <tassilo@member.fsf.org>,
5175@debbugs.gnu.org, ding@gnus.org
Subject: bug#5175: 23.1.50; mark deactivated without running deactivate-mark-hook when replying with Gnus
Date: Fri, 01 Jan 2010 21:41:59 -0500 [thread overview]
Message-ID: <87ljgh6xe0.fsf__47964.4918385476$1262400616$gmane$org@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:
> 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'?
An alternative is to avoid using exchange-point-and-mark entirely, like
this:
(goto-char (prog1 (mark t)
(set-marker (mark-marker) (point)
(current-buffer))))
(Please don't replay to emacsbugs.donarmstrong.com/debbugs.gnu.org AND
emacs-pretest-bug at the same time; sending to the latter creates a new
bug in our database.)
next prev parent reply other threads:[~2010-01-02 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r5q936a6.fsf@stupidchicken.com>
2009-12-10 15:23 ` bug#5175: 23.1.50; mark deactivated without running deactivate-mark-hook when replying with Gnus Tassilo Horn
2010-01-01 21:29 ` bug#5175: marked as done (23.1.50; mark deactivated without running deactivate-mark-hook when replying with Gnus) Emacs bug Tracking System
2010-01-02 1:38 ` bug#5175: 23.1.50; mark deactivated without running deactivate-mark-hook when replying with Gnus Katsumi Yamaoka
2010-01-02 1:38 ` Katsumi Yamaoka
[not found] ` <b4mbphdmgl7.fsf@jpl.org>
2010-01-02 2:41 ` Chong Yidong [this message]
2010-01-02 19:20 ` Chong Yidong
[not found] ` <877hs048lh.fsf@stupidchicken.com>
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='87ljgh6xe0.fsf__47964.4918385476$1262400616$gmane$org@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.
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.