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: Sat, 15 Dec 2012 12:49:36 +0200 [thread overview]
Message-ID: <87bodv1t0j.fsf@mail.jurta.org> (raw)
In-Reply-To: <50CAFE8F.2060903@gmx.at> (martin rudalics's message of "Fri, 14 Dec 2012 11:25:19 +0100")
>>> Why do you never quit the *Messages* buffer in your scenario?
>>
>> I can't quit the *Messages* buffer. Typing `q' inserts the character
>> `q' to the *Messages* buffer. But it's good that *Messages* is writable.
>> The same problem can occur with any other writable buffer.
>
> You can always do M-x quit-window. Isn't there some C-x binding we
> could use for this?
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.
> 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?
next prev parent reply other threads:[~2012-12-15 10:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bodv1t0j.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 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.