From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.devel Subject: Re: Allow controlling the effect of visibility on buffer switching Date: Sat, 29 Jan 2022 10:27:34 -0500 Message-ID: <87o83uimu1.fsf@md5i.com> References: <87a6fi3lrl.fsf@gmail.com> <83a6fihbeb.fsf@gnu.org> <877dam38zr.fsf@gmail.com> <8335lah77y.fsf@gnu.org> <87mtjf0ypz.fsf@gmail.com> <87y22yhogr.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2685"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Eli Zaretskii , Thuna , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 29 16:29:50 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nDpfh-0000Q4-Q5 for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Jan 2022 16:29:50 +0100 Original-Received: from localhost ([::1]:58112 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nDpff-0005Zj-W3 for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Jan 2022 10:29:48 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:35616) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nDpda-0004jT-Sl for emacs-devel@gnu.org; Sat, 29 Jan 2022 10:27:38 -0500 Original-Received: from md5i.com ([75.151.244.229]:54044) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nDpdY-00021R-AB; Sat, 29 Jan 2022 10:27:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=md5i.com; s=dkim; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References: Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=A9/rwpJqmjoCnv0Hg+7bXEhr9DmH27qAuFB78NkYJvA=; b=W1I+vhifsU1MK4ycKOheGxokpG d7r5+5VaHG6xq7RgHao3M2O85ZA3Zw2xclkFBLSghNE4dpAH3jghiX5s6ZnTBy8I263zne3JHXJ0U gzlusb3h3o4vcxBnVRe4NEBgC; Original-Received: from abode ([192.168.177.1] helo=miko) by md5i.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1nDpdW-005czW-CU; Sat, 29 Jan 2022 10:27:34 -0500 In-Reply-To: <87y22yhogr.fsf@yahoo.com> (Po Lu's message of "Sat, 29 Jan 2022 17:37:40 +0800") Received-SPF: pass client-ip=75.151.244.229; envelope-from=mwd@md5i.com; helo=md5i.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:285562 Archived-At: Po Lu writes: > Thuna 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)