From: martin rudalics <rudalics@gmx.at>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 4041@debbugs.gnu.org, Steve Yegge <stevey@google.com>
Subject: bug#4041: 23.0.92; Emacs 23: buffer point is no longer frame-local
Date: Fri, 07 Oct 2011 19:00:48 +0200 [thread overview]
Message-ID: <4E8F3040.1060409@gmx.at> (raw)
In-Reply-To: <m3hb3lt6xv.fsf@stories.gnus.org>
>> We'd have to handle two issues:
>>
>> (1) If a buffer is shown nowhere else and you `switch-to-buffer' to it,
>> you probably want it to show it at the actual position of `point' -
>> whatever that means for you.
>>
>> (2) If the buffer is already shown on another frame with `point' visible
>> it makes sense to `switch-to-buffer' at some position it earlier had
>> on the present frame.
>>
>> Whatever we did here, it would make `switch-to-buffer' behave
>> inconsistently.
>
> But it'd be the natural thing to do, I think.
I can't tell because I'm a single-frame user. The main argument in
favor of a "retain the previous point" strategy is that it makes no
sense to go to the same position already shown in another frame. But
then what about doing C-x b in a window below another one already
showing the buffer I want to switch to?
> People commonly use `C-x b' to switch buffers...
... and that's why I'm afraid of changing its semantics. More so
because I never use C-x b.
We could make the behavior optional but I'd like to hear more comments
from other users first. In any case this is a 24.2 project.
martin
next prev parent reply other threads:[~2011-10-07 17:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 0:17 bug#4041: 23.0.92; Emacs 23: buffer point is no longer frame-local Steve Yegge
2009-08-06 9:33 ` martin rudalics
2011-09-17 7:04 ` Lars Magne Ingebrigtsen
2011-09-17 8:43 ` martin rudalics
2011-09-18 8:03 ` Lars Magne Ingebrigtsen
2011-10-06 22:14 ` Lars Magne Ingebrigtsen
2011-10-07 7:07 ` martin rudalics
2011-10-07 10:46 ` Lars Magne Ingebrigtsen
2011-10-07 17:00 ` martin rudalics [this message]
2011-10-07 21:09 ` Steve Yegge
2011-10-08 6:23 ` Eli Zaretskii
2011-10-08 6:32 ` Drew Adams
2011-10-08 6:23 ` Leo
2011-10-08 13:23 ` martin rudalics
2011-10-08 14:12 ` Eli Zaretskii
2011-10-08 15:00 ` martin rudalics
2011-10-08 15:34 ` Eli Zaretskii
2011-10-08 15:55 ` martin rudalics
2011-10-08 17:07 ` Eli Zaretskii
2011-10-08 17:53 ` martin rudalics
2011-10-08 20:35 ` Eli Zaretskii
2011-10-09 8:33 ` martin rudalics
2011-10-09 17:45 ` Eli Zaretskii
2011-10-10 12:57 ` martin rudalics
2011-10-11 12:45 ` Stefan Monnier
2011-10-12 0:35 ` Steve Yegge
2011-10-12 1:19 ` Stefan Monnier
2011-10-12 3:52 ` Steve Yegge
2011-10-12 9:48 ` martin rudalics
2011-10-12 13:11 ` Stefan Monnier
2011-10-12 13:39 ` Stefan Monnier
2011-10-12 14:25 ` martin rudalics
2012-10-05 10:08 ` martin rudalics
2012-10-10 10:22 ` martin rudalics
2011-10-12 6:52 ` martin rudalics
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=4E8F3040.1060409@gmx.at \
--to=rudalics@gmx.at \
--cc=4041@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stevey@google.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).