From: "Richard M. Stallman" <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, 1175@emacsbugs.donarmstrong.com
Cc: 1175@emacsbugs.donarmstrong.com, cyd@stupidchicken.com,
bug-submit-list@donarmstrong.com, bug-gnu-emacs@gnu.org
Subject: bug#1175: 23.0.60; bookmark code regression
Date: Wed, 22 Oct 2008 02:20:57 -0400 [thread overview]
Message-ID: <E1KsX5V-0002yH-Ly@fencepost.gnu.org> (raw)
In-Reply-To: <009d01c933a5$e17ff690$0200a8c0@us.oracle.com> (drew.adams@oracle.com)
This is analogous to `find-file-noselect'. `bookmark-jump-noselect' is an
obvious choice for some function to call, to obtain the bookmark buffer and
buffer position. Without actually displaying it - perhaps because some other
display mechanism is preferred or perhaps because some other manipulation is to
be performed.
I agree with you.
Emacs 23 has not even been released, so please don't speak of
"changing" from the Emacs 23 behavior to what has always been the behavior
before.
You are right here too. Compatibility with past Emacs releases
is more important, generally speaking, than avoiding changes in
the sources now. I am sure this function isn't used in very many places
in Emacs, so changing it back to be compatible won't be a lot of work.
There is, BTW, nothing truly "internal" when it comes to Emacs,
especially when it comes to Emacs Lisp.
That doesn't really matter. There are functions which users should
not call, and if they do, they are out of luck when we change them.
But `bookmark-jump-noselect' should not be treated that way; it is too
natural and useful.
next prev parent reply other threads:[~2008-10-22 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:54 bug#1175: 23.0.60; bookmark code regression Chong Yidong
2008-10-21 17:53 ` Drew Adams
2008-10-22 6:20 ` Richard M. Stallman [this message]
2008-10-27 13:32 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2008-10-16 17:36 Chong Yidong
2008-10-15 20:51 Drew Adams
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=E1KsX5V-0002yH-Ly@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=1175@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=bug-submit-list@donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=drew.adams@oracle.com \
/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.