From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 13167@debbugs.gnu.org
Subject: bug#13167: 24.3.50; C-x right C-x left interferes with buffer order
Date: Sat, 15 Dec 2012 19:06:53 +0100 [thread overview]
Message-ID: <50CCBC3D.3010504@gmx.at> (raw)
In-Reply-To: <87bodv1t0j.fsf@mail.jurta.org>
> A good C-x binding for quit-window is `C-x q'. Its current command
> does nothing normally and already has an alternative keybinding
> `C-x C-k q' while recording a macro.
It's easy to convince me ...
>> this loop finds a buffer to switch to, it retrieves the start and point
>> positions from the buffer's association in the window's _previous_
>> buffers. I didn't want to maintain the same markers twice.
>
> To not maintain the same markers twice, `C-x left' could add the
> current buffer with markers only once to the list of next buffers,
> but not to the list of previous buffers. Do I miss something
> why this won't work?
If we did that, we'd probably get rid of the behavior you started this
thread with. But the current semantics is "when we have to replace a
buffer in a window with another one, try taking the buffer that has been
shown in that window before the present one". I'm not quite sure how to
describe what you want to do instead.
martin
next prev parent reply other threads:[~2012-12-15 18:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 23:37 bug#13167: 24.3.50; C-x right C-x left interferes with buffer order Juri Linkov
2012-12-13 10:29 ` martin rudalics
2012-12-14 0:45 ` Juri Linkov
2012-12-14 10:25 ` martin rudalics
2012-12-15 10:49 ` Juri Linkov
2012-12-15 18:06 ` martin rudalics [this message]
2012-12-16 9:17 ` Juri Linkov
2012-12-16 18:12 ` martin rudalics
2012-12-17 9:35 ` Juri Linkov
2012-12-17 9:57 ` Juri Linkov
2012-12-17 13:38 ` martin rudalics
2012-12-22 9:27 ` Juri Linkov
2012-12-22 15:41 ` martin rudalics
2012-12-23 9:49 ` Juri Linkov
2012-12-23 14:03 ` martin rudalics
2024-01-10 17:03 ` Juri Linkov
2024-01-11 9:15 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 7:42 ` Juri Linkov
2024-01-12 8:48 ` Eli Zaretskii
2024-01-10 11:26 ` Stefan Kangas
2024-01-10 17:01 ` Juri Linkov
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=50CCBC3D.3010504@gmx.at \
--to=rudalics@gmx.at \
--cc=13167@debbugs.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 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).