From: Eli Zaretskii <eliz@gnu.org>
To: Jefferson Carpenter <jefferson@aoeu2code.com>
Cc: 37514@debbugs.gnu.org
Subject: bug#37514: PATCH: Add setting to allow switching to an already-visible buffer by default
Date: Thu, 26 Sep 2019 10:12:23 +0300 [thread overview]
Message-ID: <83d0fnmsyw.fsf@gnu.org> (raw)
In-Reply-To: <16d6a4fecc8.102faf4a4441777.3062189885757431562@aoeu2code.com> (message from Jefferson Carpenter on Wed, 25 Sep 2019 21:24:45 +0000)
> Date: Wed, 25 Sep 2019 21:24:45 +0000
> From: Jefferson Carpenter <jefferson@aoeu2code.com>
>
> A not-uncommon workflow of mine is to have more than one window looking at the same buffer in several
> different places. Often in one of these windows I switch to some other buffer (perhaps a shell) and then want
> to switch directly back to the same place I was just looking at in main buffer. However since my main buffer is
> already visible in another window, C-x b (switch-to-buffer) does not default to that buffer, but prefers a buffer
> that is not already visible. This customization setting allows users to override that behavior so that
> switch-to-buffer does not prefer buffers that are not already visible.
Why is it important what "C-x b" offers as the default? You can still
type the name of the buffer you want and switch to it.
FWIW, I use the workflow you mention from time to time, and I never
felt the need for such an option, because its effect will be global on
the entire session, and I don't want it everywhere. I'd need to reset
such an option when I go back to the other workflows, which would be a
nuisance.
And if the above is somehow still not satisfactory, you can always
write a trivial wrapper around switch-to-buffer, which behaves the way
you like. Why do we need to canonicalize this in Emacs?
Thanks.
next prev parent reply other threads:[~2019-09-26 7:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 21:24 bug#37514: PATCH: Add setting to allow switching to an already-visible buffer by default Jefferson Carpenter
2019-09-26 7:12 ` Eli Zaretskii [this message]
2019-09-26 19:13 ` Jefferson Carpenter
2019-09-26 19:14 ` Jefferson Carpenter
2019-09-27 8:16 ` martin rudalics
2019-09-28 21:00 ` Jefferson Carpenter
2019-10-02 3:36 ` Jefferson Carpenter
2019-10-02 8:54 ` martin rudalics
2019-10-04 0:45 ` Jefferson Carpenter
2019-10-05 8:42 ` martin rudalics
2019-10-05 9:30 ` Eli Zaretskii
2020-01-20 19:35 ` Stefan Kangas
2020-03-18 5:36 ` Stefan Kangas
2019-10-07 4:25 ` Lars Ingebrigtsen
2019-10-07 9:26 ` martin rudalics
2019-10-07 18:09 ` Juri Linkov
2019-10-08 8:45 ` martin rudalics
2019-10-09 18:48 ` Juri Linkov
2019-10-12 20:47 ` Juri Linkov
2019-10-13 8:17 ` martin rudalics
2019-10-08 16:32 ` Lars Ingebrigtsen
2019-10-09 20:50 ` Juri Linkov
2019-10-09 20:59 ` Lars Ingebrigtsen
2019-10-11 8:16 ` martin rudalics
2019-10-07 12:04 ` Robert Pluim
2019-10-08 8:42 ` martin rudalics
2019-10-08 11:42 ` Robert Pluim
2019-09-26 7:20 ` martin rudalics
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=83d0fnmsyw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37514@debbugs.gnu.org \
--cc=jefferson@aoeu2code.com \
/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.