From: Richard Stallman <rms@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org
Subject: Re: gnus-summary-catchup turns ticked into unread
Date: Mon, 06 Aug 2007 10:22:36 -0400 [thread overview]
Message-ID: <E1II3Tg-0000zH-8P@fencepost.gnu.org> (raw)
In-Reply-To: <b4mps2zzivn.fsf@jpl.org> (message from Katsumi Yamaoka on Wed, 11 Jul 2007 13:03:56 +0900)
The function definition for the XEmacs version of pop-to-buffer
is as follows. There's no difference between XEmacs 21.4 and 21.5.
The optional ON-FRAME is boolean, so there seems no way to keep
the compatibility.
(defun pop-to-buffer (bufname &optional not-this-window-p on-frame)
...
If optional third arg is non-nil, it is the frame to pop to this
buffer on.
I am sure that few callers pass the argument NORECORD to
pop-to-buffer. So I think an incompatible change would be ok, adding
the ON-FRAME argument before NORECORD.
What do others think?
next parent reply other threads:[~2007-08-06 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070702160929.C21251C8115@galatea.esat.kuleuven.be>
[not found] ` <b4mmyydn5r2.fsf@jpl.org>
[not found] ` <b4m64501nt8.fsf@jpl.org>
[not found] ` <E1I6GBH-0006d2-HI@fencepost.gnu.org>
[not found] ` <b4mejjn1usy.fsf@jpl.org>
[not found] ` <E1I6Y2D-00062v-Iq@fencepost.gnu.org>
[not found] ` <b4mr6nhjgq1.fsf@jpl.org>
[not found] ` <E1I8Nlq-0000oX-F6@fencepost.gnu.org>
[not found] ` <b4mps2zzivn.fsf@jpl.org>
2007-08-06 14:22 ` Richard Stallman [this message]
2007-08-14 0:28 ` gnus-summary-catchup turns ticked into unread Richard Stallman
2007-08-16 1:54 ` Katsumi Yamaoka
2007-08-16 18:39 ` Richard Stallman
2007-08-17 1:22 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1II3Tg-0000zH-8P@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).