unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thuna <thuna.cing@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Allow controlling the effect of visibility on buffer switching
Date: Wed, 26 Jan 2022 17:01:05 +0200	[thread overview]
Message-ID: <8335lah77y.fsf@gnu.org> (raw)
In-Reply-To: <877dam38zr.fsf@gmail.com> (message from Thuna on Wed, 26 Jan 2022 16:46:32 +0300)

> From: Thuna <thuna.cing@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Wed, 26 Jan 2022 16:46:32 +0300
> 
> 
> > Thanks, but why do we need such an option, given that we have
> > buffer-change history, and so the visible buffers are usually just a
> > couple of keystrokes away, like M-n?
> 
> If a buffer is open in multiple windows and one of these windows is
> momentarily switched off of to look at something else, it is unintuitive
> for buffer switching to default to a non-visible buffer instead of the
> previously open buffer.  More often than not, a quick [C-x b RET] is,
> and should be, sufficient for switching buffers.  Forcing the user to
> actively choose the buffer they want introduces unnecessary burden which
> can be a significant source of distraction over time.

Forcing users to learn too many options is also not a very good idea,
and we already have gobs of them.  So much so that even the head
maintainers don't remember that many of them exist.

So I'm asking whether "C-x b M-n RET" is not a good enough solution
for this use case?  Does anyone else have an opinion?



  reply	other threads:[~2022-01-26 15:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  9:10 Allow controlling the effect of visibility on buffer switching Thuna
2022-01-26 13:30 ` Eli Zaretskii
2022-01-26 13:46   ` Thuna
2022-01-26 15:01     ` Eli Zaretskii [this message]
2022-01-27  3:18       ` Matt Armstrong
2022-01-27 18:16         ` Thuna
2022-01-27  4:25       ` Michael Welsh Duggan
2022-01-27 17:09       ` Juri Linkov
2022-01-29  7:48       ` Thuna
2022-01-29  8:14         ` Eli Zaretskii
2022-01-29  8:35           ` Thuna
2022-01-29  9:37         ` Po Lu
2022-01-29 15:27           ` Michael Welsh Duggan
2022-01-29 20:03             ` chad
2022-01-30  7:06               ` Po Lu
2022-01-30  0:31           ` Stefan Monnier
2022-01-30  6:42             ` Eli Zaretskii
2022-01-30 16:08               ` Stefan Monnier
2022-01-30 16:51                 ` Eli Zaretskii

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=8335lah77y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=thuna.cing@gmail.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 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).