all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thuna <thuna.cing@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Allow controlling the effect of visibility on buffer switching
Date: Sat, 29 Jan 2022 10:48:08 +0300	[thread overview]
Message-ID: <87mtjf0ypz.fsf@gmail.com> (raw)
In-Reply-To: <8335lah77y.fsf@gnu.org>


> 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.

If the proposal is rejected on this basis, I would like to revise it
from "introducing an option to change the behavior of switch-to-buffer"
to "changing the behavior of switch-to-buffer".

It is extremely unlikely for someone to know what their last non-visible
buffer is, especially after accounting for other frames and windows.
People are better off typing the name of the buffer they want to visit.
Compared to that, switching to the last buffer is considerably more
manageable and useful.



  parent reply	other threads:[~2022-01-29  7:48 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mtjf0ypz.fsf@gmail.com \
    --to=thuna.cing@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 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.