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 09:07:14 +0200 [thread overview]
Message-ID: <4E8EA522.9090300@gmx.at> (raw)
In-Reply-To: <m3r52pg442.fsf@stories.gnus.org>
>> Even if you had such a feature it would not DTRT with multiple windows
>> showing the same buffer on the same frame. But if, in step (9) above,
>> you do `previous-buffer' or `switch-to-prev-buffer', the window's point
>> should show up at `point-min'. `switch-to-buffer' could, in principle,
>> retrieve that position by scanning `window-prev-buffers' of that window.
>
> I think `switch-to-buffer' should do the same as `previous-buffer' here
> -- it seems like the obvious solution. Is there any reason not to?
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. I still think that the OP instead of
> 8) switch to buffer *scratch* (or any other buffer)
> 9) switch to buffer BUF
should switch to the previous buffer in 9).
martin
next prev parent reply other threads:[~2011-10-07 7:07 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 [this message]
2011-10-07 10:46 ` Lars Magne Ingebrigtsen
2011-10-07 17:00 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E8EA522.9090300@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 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.