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.bugs Subject: bug#69983: Use category for display-buffer-alist Date: Thu, 18 Apr 2024 20:56:39 +0300 Message-ID: <86h6fyd06g.fsf@gnu.org> References: <86h6gv7e0z.fsf@mail.linkov.net> <86sezyjpsn.fsf@mail.linkov.net> <86a5m3jboy.fsf@mail.linkov.net> <86v84rvwpa.fsf@gnu.org> <867ch7gfa4.fsf@mail.linkov.net> <86bk6iwftq.fsf@gnu.org> <86il0pd8da.fsf@mail.linkov.net> <864jc9wk5r.fsf@gnu.org> <861q7dgla3.fsf@mail.linkov.net> <86il0pulum.fsf@gnu.org> <86cyqwjtpr.fsf@mail.linkov.net> <86y19ktkj2.fsf@gnu.org> <86h6g7m773.fsf@mail.linkov.net> <86sezrrrgh.fsf@gnu.org> <86il0m7ceo.fsf@mail.linkov.net> <86a5lysah3.fsf@gnu.org> <86o7ad2j84.fsf@mail.linkov.net> <86mspxnkyt.fsf@gnu.org> <86bk6c5ke3.fsf@mail.linkov.net> <864jbyeo9y.fsf@gnu.org> <86jzkusidd.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24143"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, 69983@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Apr 18 19:58:09 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1rxW1Q-00067R-V8 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Apr 2024 19:58:09 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rxW19-00083o-Rq; Thu, 18 Apr 2024 13:57:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rxW17-00083O-0I for bug-gnu-emacs@gnu.org; Thu, 18 Apr 2024 13:57:49 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rxW16-0000cG-Nb for bug-gnu-emacs@gnu.org; Thu, 18 Apr 2024 13:57:48 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rxW1K-0000RG-8t for bug-gnu-emacs@gnu.org; Thu, 18 Apr 2024 13:58:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 18 Apr 2024 17:58:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69983 X-GNU-PR-Package: emacs Original-Received: via spool by 69983-submit@debbugs.gnu.org id=B69983.17134630261306 (code B ref 69983); Thu, 18 Apr 2024 17:58:02 +0000 Original-Received: (at 69983) by debbugs.gnu.org; 18 Apr 2024 17:57:06 +0000 Original-Received: from localhost ([127.0.0.1]:53750 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rxW0N-0000Kc-Q4 for submit@debbugs.gnu.org; Thu, 18 Apr 2024 13:57:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53992) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rxW0L-0000J8-IT for 69983@debbugs.gnu.org; Thu, 18 Apr 2024 13:57:02 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rxW01-0000QI-Ny; Thu, 18 Apr 2024 13:56:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Ovaqu3ebwR5kW++Wif9j+BmsJnCk4wWpKXQ8DKDyp0g=; b=U7qVNdTm+4Oo CRqDUykv39z3X17iDuZxLviVxTkLMFqgwUa367ZfQtHALdaovWoqhPBU10BLyIsWnnHg5e0iuTMpI NpChY6qq8ho5IZ/cCkJzoZ8/YiW/D/I+PAcc2VhHaLSa/G5hd5sXrKUdK74sBVO4YuP4Ucts/GuYh 4Irr1azATWQvsjwWm3N7A38afGSOnCcN4iZaVTG7lIqdrvg8M/WIrs4ekJ+dYFO8VFN1fYSQJDAmZ UEqWoCcHzl7Q7TtOOiyPgKCV2E7k1WnYHZmOKnWsF/y7T1UXB3Ja2PRbukfV1W/9eJopIFAo4FgsZ GVtA+ifltEZQYfo9m8L96Q==; In-Reply-To: <86jzkusidd.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 18 Apr 2024 20:16:30 +0300) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:283601 Archived-At: > From: Juri Linkov > Cc: rudalics@gmx.at, 69983@debbugs.gnu.org > Date: Thu, 18 Apr 2024 20:16:30 +0300 > > >> >> > If we want to enable user control of displaying warnings, we will have > >> >> > to add an option for that, because currently that cannot be > >> >> > controlled. display-buffer-alist is inappropriate for such control, > >> >> > since in some cases warnings are not displayed in pop-up windows. > >> >> > >> >> Could you show an example when warnings are not displayed in pop-up windows. > >> > > >> > The two calls to 'message' there. > >> > >> These calls are irrelevant. It makes no sense to add an option > >> to display text "at the bottom of 'message'". > > > > Of course. But what if some user would like to display the warnings > > in the echo-area? Don't we want to allow such customization? If we > > do, then display-buffer machinery is not relevant, exactly as it is > > not relevant for those two calls. > > This proves that a new option is not needed. QED. > > >> >> > Thanks, but what do you mean by "at the bottom"? Can you describe > >> >> > that place more precisely? > >> >> > >> >> Here is an example: > >> > > >> > I understand what this means in the simple cases, but not necessarily > >> > what happens in more complex cases. > >> > >> This case is not simple. It demonstrates the problem > >> in horizontally split windows. > >> > >> > This is why I asked for a detailed definition of "at bottom". > >> > >> The detailed definition is in the documentation of > >> 'display-buffer-at-bottom'. > > > > I agree that "display at bottom" is a useful feature, but why should > > we decide that users could have no control of that, either? E.g., > > another reasonable MO is to split the selected window vertically and > > show the warning in the lower window. > > This is easy to customize with a category in display-buffer-alist. > > > So I think display-warning should have a variable to customize its > > display, and limiting that only to what display-buffer can produce > > doesn't support all the optional behaviors people could reasonably > > want. Moreover, display-buffer is IMO overly-complex for this simple > > job; a simple variable with several distinct values would do. > > Adding dozens of new variables that replace display-buffer-alist > makes no sense. So we disagree. I stand by my opinion, and will object to making display-buffer-alist the way of customizing display-warning.