From: Juri Linkov <juri@jurta.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 13167@debbugs.gnu.org
Subject: bug#13167: 24.3.50; C-x right C-x left interferes with buffer order
Date: Mon, 17 Dec 2012 11:35:31 +0200 [thread overview]
Message-ID: <87a9tdyqak.fsf@mail.jurta.org> (raw)
In-Reply-To: <50CE0EFD.3010505@gmx.at> (martin rudalics's message of "Sun, 16 Dec 2012 19:12:13 +0100")
>> I believe C-x right and C-x left should be special to not affect the
>> logic of "try taking the buffer that has been shown in that window
>> before the present one".
>
> I'm not sure what this means to do instead. Have `quit-window' not show
> a buffer if it appears on `window-next-buffers'?
Thanks, this sounds right.
> What happens if you turn the form
>
> (or bury-or-kill (not (memq buffer next-buffers))))
>
> in `switch-to-prev-buffer' into
>
> (not (memq buffer next-buffers)))
I tried to do this but with no effect. Then I also turned
(or bury-or-kill (not (memq new-buffer next-buffers))))
in `switch-to-prev-buffer' into
(not (memq new-buffer next-buffers)))
and it works as expected. Not sure about possible side-effects,
have to test this change more.
next prev parent reply other threads:[~2012-12-17 9:35 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
2012-12-16 9:17 ` Juri Linkov
2012-12-16 18:12 ` martin rudalics
2012-12-17 9:35 ` Juri Linkov [this message]
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=87a9tdyqak.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=13167@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).