From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: Chong Yidong <cyd@gnu.org>, emacs-devel@gnu.org
Subject: Re: window-next-buffers
Date: Fri, 25 Nov 2011 11:15:45 +0100 [thread overview]
Message-ID: <4ECF6AD1.1070807@gmx.at> (raw)
In-Reply-To: <8739dduz0q.fsf@mail.jurta.org>
> This sounds like an overly optimization. But actually I can't find
> a case where `next-buffer' would fail to get information about markers.
> Is this because information about markers of next buffers is retrieved
> from `window-prev-buffers'?
Yes. In `switch-to-next-buffer'
(assq buffer (window-prev-buffers window))
provides this information. `window-next-buffers' is exclusively used
for buffer navigation within a window. `window-prev-buffers' is used in
other occasions like `quit-window' where I don't care about a window's
next buffers.
> Isn't better to push a new window to the top of the list of next buffers
> to not lose information about the rest of next buffers?
Can you elaborate what you mean here? A new window has neither previous
nor next buffers.
martin
next prev parent reply other threads:[~2011-11-25 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 7:58 window-next-buffers Chong Yidong
2011-11-24 9:24 ` window-next-buffers Chong Yidong
2011-11-24 10:07 ` window-next-buffers martin rudalics
2011-11-24 9:59 ` window-next-buffers martin rudalics
2011-11-24 19:00 ` window-next-buffers Juri Linkov
2011-11-25 10:15 ` martin rudalics [this message]
2011-11-25 10:33 ` window-next-buffers Juri Linkov
2011-11-25 13:55 ` window-next-buffers martin rudalics
2011-11-25 15:11 ` window-next-buffers Stephen J. Turnbull
2011-11-25 16:05 ` window-next-buffers Chong Yidong
2011-11-25 19:02 ` window-next-buffers Juri Linkov
2011-11-26 6:59 ` window-next-buffers Chong Yidong
2011-11-26 11:44 ` window-next-buffers 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=4ECF6AD1.1070807@gmx.at \
--to=rudalics@gmx.at \
--cc=cyd@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
/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.