From: martin rudalics <rudalics@gmx.at>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: 6454@debbugs.gnu.org
Subject: bug#6454: 24.0.50; kill-buffer switches current-buffer
Date: Fri, 18 Jun 2010 14:19:09 +0200 [thread overview]
Message-ID: <4C1B643D.1080703@gmx.at> (raw)
In-Reply-To: <m28w6csiio.fsf@gmail.com>
> (goto-line 1 buffer))
makes sure there's a window showing BUFFER and selects that window.
> (kill-buffer buffer)
detects that the window showing BUFFER is the selected window, shows
another buffer in that window, and makes the other buffer current.
Tha according lines in window_loop are:
Fset_window_buffer (window, buffer, Qnil);
if (EQ (window, selected_window))
Fset_buffer (w->buffer);
with the most recent change
1989-10-21 Richard Stallman (rms@sugar-bombs.ai.mit.edu)
* window.c (window_loop): For UNSHOW_BUFFER, don't Fset_buffer
unless window is the selected one.
So this is another incarnation of the "buffer shown in the selected
window is not necessarily the current buffer" dichotomy. Looks like
a bug but I'm not sure whether fixing it could break other things.
martin
next prev parent reply other threads:[~2010-06-18 12:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 11:10 bug#6454: 24.0.50; kill-buffer switches current-buffer Helmut Eller
2010-06-18 12:19 ` martin rudalics [this message]
2010-06-18 13:54 ` Stefan Monnier
2010-06-18 14:33 ` martin rudalics
2010-06-18 15:33 ` Stefan Monnier
2010-06-18 19:12 ` martin rudalics
2010-06-18 22:30 ` martin rudalics
2010-06-19 13:38 ` martin rudalics
2010-06-20 7:48 ` Helmut Eller
2010-06-20 10:42 ` martin rudalics
2010-06-20 18:00 ` Helmut Eller
2010-06-21 10:46 ` martin rudalics
2010-06-21 14:25 ` Helmut Eller
2010-06-21 15:49 ` martin rudalics
2010-06-21 16:19 ` Helmut Eller
2010-06-21 17:38 ` martin rudalics
2011-09-21 20:44 ` Lars Magne Ingebrigtsen
2011-09-22 7:07 ` Helmut Eller
2011-09-23 10:56 ` Lars Magne Ingebrigtsen
2010-06-24 23:07 ` Stefan Monnier
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=4C1B643D.1080703@gmx.at \
--to=rudalics@gmx.at \
--cc=6454@debbugs.gnu.org \
--cc=eller.helmut@gmail.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 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).