unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 17 Dec 2012 14:38:34 +0100	[thread overview]
Message-ID: <50CF205A.50004@gmx.at> (raw)
In-Reply-To: <87fw35vvzf.fsf@mail.jurta.org>

 > There is one side-effect with overwrapping in next buffers.
 > When `C-x right C-x right' wraps to the first buffer *scratch*,
 > *scratch* is pushed to the list of next buffers.
 >
 > Then `C-x left C-x left' returns to the previous buffers,
 > typing `q' restores the right buffer, another `q' restores
 > another right buffer.  But the last `q' doesn't restore
 > the buffer *scratch*.
 >
 > This is in the following scenario:
 >
 >  1. emacs -Q
 >  2. C-h C-n
 >  3. C-x d RET
 >  4. v
 >  5. C-x right    displays the buffer *Messages*
 >  6. C-x right    displays the buffer *scratch*
 >  7. C-x left
 >  8. C-x left
 >  9. q
 > 10. q
 > 11. q
 > 12. q   the last q doesn't restore the initial buffer *scratch*

Is the list of previous buffers empty in step 12 ?  Then we could
heuristically show the last buffer added to the list of next buffers
here.  Preferring a buffer which is not on any of this window's lists
doesn't make much sense in this case, I think.

I guess that this scenario would also break the recipe you proposed
earlier, namely to keep next and previous buffers as lists built from
elements of the same type and not choose an element from the next
buffers when quitting.

martin





  reply	other threads:[~2012-12-17 13:38 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
2012-12-17  9:57                 ` Juri Linkov
2012-12-17 13:38                   ` martin rudalics [this message]
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=50CF205A.50004@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).