From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#69983: Use category for display-buffer-alist Date: Thu, 11 Apr 2024 09:31:45 +0300 Organization: LINKOV.NET Message-ID: <86cyqwjtpr.fsf@mail.linkov.net> References: <86h6gv7e0z.fsf@mail.linkov.net> <3e7b8e64-0a5f-4888-a443-9c69a5fffd98@gmx.at> <86wmpdu0fa.fsf@mail.linkov.net> <86h6gf69jd.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28813"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: rudalics@gmx.at, 69983@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Apr 11 08:36:17 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 1ruo2j-0007M9-LO for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 11 Apr 2024 08:36:17 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ruo2O-0004ZW-EB; Thu, 11 Apr 2024 02:35:56 -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 1ruo2L-0004Z6-Gm for bug-gnu-emacs@gnu.org; Thu, 11 Apr 2024 02:35:53 -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 1ruo2L-0006Vm-8o for bug-gnu-emacs@gnu.org; Thu, 11 Apr 2024 02:35:53 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ruo2U-00063R-9N for bug-gnu-emacs@gnu.org; Thu, 11 Apr 2024 02:36:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 11 Apr 2024 06:36: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.171281732022979 (code B ref 69983); Thu, 11 Apr 2024 06:36:02 +0000 Original-Received: (at 69983) by debbugs.gnu.org; 11 Apr 2024 06:35:20 +0000 Original-Received: from localhost ([127.0.0.1]:54778 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ruo1n-0005yM-AJ for submit@debbugs.gnu.org; Thu, 11 Apr 2024 02:35:19 -0400 Original-Received: from relay8-d.mail.gandi.net ([217.70.183.201]:60361) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ruo1j-0005wz-IZ for 69983@debbugs.gnu.org; Thu, 11 Apr 2024 02:35:17 -0400 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 09D631BF209; Thu, 11 Apr 2024 06:34:58 +0000 (UTC) In-Reply-To: <86il0pulum.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Apr 2024 21:13:53 +0300") X-GND-Sasl: juri@linkov.net 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:283080 Archived-At: >> > More importantly, if we want to let programs and users control where >> > the warnings are displayed, I'd rather we introduced a new, >> > warning.el-specific option. Up front, there's no reason for anyone to >> > assume that display-buffer-alist will have _any_ effect on >> > display-warning, because we don't document that display-warning uses >> > display-buffer. So we could one day decide to implement the display >> > of the warnings in an entirely different fashion, and then no >> > customizations of display-buffer-alist will be able to affect the >> > display. In fact, in some situations we already display the warning >> > other than via display-buffer. >> >> These are just excuses to not make life easier for users of >> horizontally split windows. > > I don't see how a warning-specific option could be an "excuse". It > can solve the problem you attempt to solve as well as what you > propose. There is already the option display-buffer-alist.