unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Thuna <thuna.cing@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: Allow controlling the effect of visibility on buffer switching
Date: Sat, 29 Jan 2022 17:37:40 +0800	[thread overview]
Message-ID: <87y22yhogr.fsf@yahoo.com> (raw)
In-Reply-To: <87mtjf0ypz.fsf@gmail.com> (Thuna's message of "Sat, 29 Jan 2022 10:48:08 +0300")

Thuna <thuna.cing@gmail.com> writes:

> It is extremely unlikely for someone to know what their last non-visible
> buffer is, especially after accounting for other frames and windows.

I find it sufficient to take a quick glance at the frame I'm currently
working on.  Further more, multiple frame workflows are reasonably rare,
and even more so the workflows where some frames aren't visible at any
given time.

And please don't change the behaviour of `switch-to-buffer' in such a
drastic manner.  People are used to it as it is.

Thanks.



  parent reply	other threads:[~2022-01-29  9:37 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
2022-01-29  9:37         ` Po Lu [this message]
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=87y22yhogr.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=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).