From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, stevey@google.com, 4041@debbugs.gnu.org
Subject: bug#4041: 23.0.92; Emacs 23: buffer point is no longer frame-local
Date: Mon, 10 Oct 2011 14:57:11 +0200 [thread overview]
Message-ID: <4E92EBA7.3090000@gmx.at> (raw)
In-Reply-To: <83hb3idpo6.fsf@gnu.org>
> I tried it now. It seems to do a good job, but it sometimes loses one
> of the 2 places in one of the files I visited. E.g., visit xdisp.c
> and window.c, display each one in turn in 2 separate windows at 2
> different places. Then start switching buffers in both windows, and
> after a few switches I can only see one place in window.c.
My crystal ball tells me that you did the following:
(1) Remove one of these buffers from the last window that shows it -
`point' goes to its `window-point'.
(2) Show this buffer in the other window.
In this case the test
(let* ((entry (and (get-buffer-window buffer 0)
(assq buffer (window-prev-buffers))))
will fail and the buffer will be shown at the position of its `point'.
Try
(let* ((entry (and ; (get-buffer-window buffer 0)
(assq buffer (window-prev-buffers))))
and I'm sure the function will do what you want.
Unfortunately, omitting that conjunct might give surprising results when
you switch to a buffer that you haven't seen for quite some time, in a
window where this buffer was shown earlier. In this case you probably
do want to show the buffer at the position of `point'.
martin
next prev parent reply other threads:[~2011-10-10 12:57 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 [this message]
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=4E92EBA7.3090000@gmx.at \
--to=rudalics@gmx.at \
--cc=4041@debbugs.gnu.org \
--cc=eliz@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.