all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Welsh Duggan <mwd@md5i.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Thuna <thuna.cing@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Allow controlling the effect of visibility on buffer switching
Date: Sat, 29 Jan 2022 10:27:34 -0500	[thread overview]
Message-ID: <87o83uimu1.fsf@md5i.com> (raw)
In-Reply-To: <87y22yhogr.fsf@yahoo.com> (Po Lu's message of "Sat, 29 Jan 2022 17:37:40 +0800")

Po Lu <luangruo@yahoo.com> writes:

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

On the other hand, I've hated the current behavior for years (as does a
colleague of mine), and it is not an easy behavior to patch in one's
local emacs, as it is buried too deeply.  I would like some way to patch
this without having to copy the innards of read-buffer-to-switch.  I
personally think that Thuna's patch is ideal, since it doesn't change
the current behavior by default but makes it easy for those of us who
want it to change to do so.  But I would take any change that makes it
easier to patch in what we consider more desirable behavior.

-- 
Michael Welsh Duggan
(md5i@md5i.com)



  reply	other threads:[~2022-01-29 15:27 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
2022-01-29 15:27           ` Michael Welsh Duggan [this message]
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=87o83uimu1.fsf@md5i.com \
    --to=mwd@md5i.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --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 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.