From: martin rudalics <rudalics@gmx.at>
To: Steve Yegge <stevey@google.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 4041@debbugs.gnu.org
Subject: bug#4041: 23.0.92; Emacs 23: buffer point is no longer frame-local
Date: Wed, 12 Oct 2011 08:52:38 +0200 [thread overview]
Message-ID: <4E953936.3020006@gmx.at> (raw)
In-Reply-To: <CAEYe22VxWEtHmy9OVPzcnoyH=gM+5UuNW79YnbAaAGJSfY1fzg@mail.gmail.com>
> In particular, if you are switching to a buffer that is already showing in
> another window, it currently takes you to to a location in that buffer that
> can best be described as "arbitrary". I was generously assuming that it was
> some deterministic function of how the buffer is already being displayed in
> other windows, but Martin claims that no, it just shows you "somewhere" in
> the buffer, wherever that window-point happens to be. It's certainly not
> semantically meaningful to the contents of the buffer.
I never claimed that
it just shows you "somewhere" in the buffer, wherever that
window-point happens to be
Such a sentence doesn't make sense. To clarify: If `switch-to-buffer'
shows a buffer in a new window or in a window that showed another buffer
before, it takes you to the position of `point' of the buffer you switch
to. This is not an arbitrary position.
> My proposal -- which people sound like they agree with, and Leo has even
> implemented as an add-on -- takes the default behavior from arbitrary to not
> only predictable but in fact useful. The only way anyone would even notice
> that you've changed something is if they were somehow relying on the
> arbitrary default behavior, but as we've determined that it's not especially
> predictable, I don't see how anyone could have been relying on it. If we're
> really worried about it, we can make a compatibility variable.
If you can specify a behavior that is predictable I'll be all ears.
Meanwhile I invite you to test the function I attached in my answer to
your earlier post, maybe together with the change I posted later in a
response to Eli, and tell me why the one or the other does not do what
you proposed.
martin
prev parent reply other threads:[~2011-10-12 6:52 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
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 [this message]
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=4E953936.3020006@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).