From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 69993@debbugs.gnu.org
Subject: bug#69993: Wrap window buffers while cycling
Date: Fri, 29 Mar 2024 18:35:12 +0200 [thread overview]
Message-ID: <86v855ggkv.fsf@mail.linkov.net> (raw)
In-Reply-To: <f3c9969f-64a0-491b-a5a8-7417a2cb9d45@gmx.at> (martin rudalics's message of "Fri, 29 Mar 2024 09:45:24 +0100")
>>> (1) The classic behavior where switching may show a buffer never shown
>>> in the window before. I suppose you mean that
>>> 'switch-to-prev-buffer-wrap' does not affect it. If that's the
>>> case, please say so.
>>
>> Indeed, 'switch-to-prev-buffer-wrap' does not affect it.
>> Switching to a buffer that was never shown in the window
>> should still reset the list of next-buffers to nil.
>>
>>> (2) The new behavior where switching may only show buffers shown in that
>>> window before. For this you want to either wrap or not. So the
>>> option 'switch-to-prev-buffer-wrap' will affect (2) only. Right?
>>
>> 'switch-to-prev-buffer-wrap' will affect only 'C-x C-left' and 'C-x C-right'
>> cycling buffers shown in that window before.
>
> I'm still confused. Do you mean that C-x b, when it switches to a
> buffer previously shown in that window, should not change the ordering
> of buffers previously shown in that window? And behave so if and only
> if 'switch-to-prev-buffer-wrap' is non-nil? Then what would users do if
> they (1) want to use your new option but (2) still want C-x b or C-x
> C-left make that buffer the most previously used one in that window?
Sorry for the confusion. This feature request was only about C-x C-left.
C-x b was just speculation about a possible separate option.
next prev parent reply other threads:[~2024-03-29 16:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 7:42 bug#69993: Wrap window buffers while cycling Juri Linkov
2024-03-25 9:41 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-25 17:16 ` Juri Linkov
2024-03-26 9:56 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-27 7:20 ` Juri Linkov
2024-03-27 8:48 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 7:54 ` Juri Linkov
2024-03-28 9:19 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 17:57 ` Juri Linkov
2024-03-29 8:45 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-29 16:35 ` Juri Linkov [this message]
2024-03-30 9:37 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-30 18:24 ` Juri Linkov
2024-03-31 8:32 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-02 6:37 ` Juri Linkov
2024-04-02 8:22 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-02 16:28 ` Juri Linkov
2024-04-03 8:24 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-03 17:45 ` Juri Linkov
2024-04-04 8:03 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-05 6:45 ` Juri Linkov
2024-04-05 9:08 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-05 16:32 ` Juri Linkov
2024-04-06 18:43 ` Juri Linkov
2024-04-07 8:23 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 6:35 ` Juri Linkov
2024-04-09 9:04 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 16:37 ` Juri Linkov
2024-04-10 8:46 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-10 17:45 ` Juri Linkov
2024-04-11 9:18 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-12 6:35 ` Juri Linkov
2024-04-12 8:37 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-12 16:23 ` Juri Linkov
2024-04-14 16:15 ` Juri Linkov
2024-04-16 6:38 ` Juri Linkov
2024-04-17 17:56 ` Juri Linkov
2024-04-24 16:39 ` Juri Linkov
2024-04-25 8:31 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-25 17:40 ` Juri Linkov
2024-04-02 16:34 ` Juri Linkov
2024-04-03 8:24 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-03 17:44 ` Juri Linkov
2024-04-04 6:22 ` Juri Linkov
2024-04-02 16:40 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v855ggkv.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=69993@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 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.