From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: feature/icomplete-vertical Date: Mon, 05 Oct 2020 22:24:47 +0300 Message-ID: <83v9fobhmo.fsf@gnu.org> References: <838sd4z6lz.fsf@gnu.org> <20201001164804.mqqyxtet4ttweuyv@Ergus> <83blhhdy3w.fsf@gnu.org> <87d01xghmt.fsf@gmail.com> <83sgatc8er.fsf@gnu.org> <83mu11c78j.fsf@gnu.org> <87tuv9eygk.fsf@gmail.com> <87imbogb6k.fsf@gmail.com> <83eemcdgg2.fsf@gnu.org> <83d01wdf8p.fsf@gnu.org> <838sckdby8.fsf@gnu.org> <87v9foeb8p.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33728"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ghe@sdf.org, spacibba@aol.com, juri@linkov.net, casouri@gmail.com, emacs-devel@gnu.org To: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 05 21:26:19 2020 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 1kPW7n-0008dZ-Fc for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Oct 2020 21:26:19 +0200 Original-Received: from localhost ([::1]:39242 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kPW7m-0004hO-HY for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Oct 2020 15:26:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51158) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kPW6M-0003dL-9t for emacs-devel@gnu.org; Mon, 05 Oct 2020 15:24:50 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36777) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kPW6J-0003d1-BM; Mon, 05 Oct 2020 15:24:47 -0400 Original-Received: from [176.228.60.248] (port=3727 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kPW6I-0007mU-NU; Mon, 05 Oct 2020 15:24:47 -0400 In-Reply-To: <87v9foeb8p.fsf@gmail.com> (message from =?utf-8?B?Sm/Do28g?= =?utf-8?B?VMOhdm9yYQ==?= on Mon, 05 Oct 2020 20:14:30 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:257142 Archived-At: > From: João Távora > Cc: Gregory Heytings , spacibba@aol.com, emacs-devel@gnu.org, > casouri@gmail.com, juri@linkov.net > Date: Mon, 05 Oct 2020 20:14:30 +0100 > > > I'm not sure what detail I need to provide. Isn't it clear that using > > a buffer-local variable doesn't resolve problems with using that same > > buffer in another level of recursive-edit? Or that changing the > > window-start position from under the feet of the display engine is > > something that should be avoided? Why would you need examples to > > realize that a design based on this cannot be clean, in the sense that > > use cases where it causes trouble will eventually surface? > > I think can understand some of Gregory's frustration. If those problems > are real, it should be possible to showcase them. The second one was showcased by Gregory himself. The first one should be clear: binding a local variable to a value will have that value in effect for all the recursive uses of the same minibuffer, something that isn't necessarily expected by the nested users. > Though that's not always easy to do, those examples could better > illustrate where the fractures in Gregory's design are, and > encourage him to undestand the problem and find alternatives. Sorry, I'm unable to encourage Gregory to understand the shortcomings, no matter how much I tried, I guess it's my fault. Although it sounds like the same situation is repeating with Martin's advice regarding mini-window resizing, so maybe it isn't entirely my fault after all.