unofficial mirror of emacs-devel@gnu.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 11:35:41 +0300	[thread overview]
Message-ID: <87k0ej0wiq.fsf@gmail.com> (raw)
In-Reply-To: <83tudnarhx.fsf@gnu.org>


> Maybe I don't understand what you mean, but "C-x b" shows the buffer
> it would switch to in the prompt, and AFAIU that is the "last
> non-visible buffer" to which you allude above, right?

It is usually the case that people have a specific buffer in mind that
they want to switch to.  If they know that that specific buffer is the
last, be it visible or non-visible, buffer that they visited, then they
can save time by hitting RET without seeing the default.  My point here
was that it is much more likely that someone knows what their last
buffer is than it is that someone knows what their last /non-visible/
buffer is.




  reply	other threads:[~2022-01-29  8:35 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
2022-01-29  8:14         ` Eli Zaretskii
2022-01-29  8:35           ` Thuna [this message]
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=87k0ej0wiq.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 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).