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: Wed, 10 Apr 2024 14:07:28 +0300 Message-ID: <864jc9wk5r.fsf@gnu.org> 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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15604"; 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 Wed Apr 10 13:08:26 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 1ruVoY-0003s7-Dq for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 10 Apr 2024 13:08:26 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ruVo7-0002KB-Sn; Wed, 10 Apr 2024 07:07:59 -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 1ruVo3-0002JS-Go for bug-gnu-emacs@gnu.org; Wed, 10 Apr 2024 07:07:55 -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 1ruVo3-0007sc-8O for bug-gnu-emacs@gnu.org; Wed, 10 Apr 2024 07:07:55 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ruVoA-0003zC-GG for bug-gnu-emacs@gnu.org; Wed, 10 Apr 2024 07:08: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: Wed, 10 Apr 2024 11:08: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.171274727015304 (code B ref 69983); Wed, 10 Apr 2024 11:08:02 +0000 Original-Received: (at 69983) by debbugs.gnu.org; 10 Apr 2024 11:07:50 +0000 Original-Received: from localhost ([127.0.0.1]:52221 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ruVny-0003ym-0d for submit@debbugs.gnu.org; Wed, 10 Apr 2024 07:07:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34288) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ruVnt-0003yX-Uy for 69983@debbugs.gnu.org; Wed, 10 Apr 2024 07:07:48 -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 1ruVnf-0007mT-Fj; Wed, 10 Apr 2024 07:07:31 -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=bEzyG5LO072EYl3RImw1ao7N91VDvAil/prPmTa/P3U=; b=Sa18NqZG4n7M ZlKlZIE51Hh0uUeJh+YlXTIJHZvLyXIRkTqtXszQeTfm/TmKBYx+iRRkA/vXjS79slAKAo50A6Ork 4bqRFcXY4fxg1EEDpHdMMAWCpHJW/MVx2LaXyD6eFWyzhn9OODouedhK5aBQoUDCEMWakJEWwrrLi ncqDylYqWzM5cbCHOMAQqcxkkM9t+QDAY6L22f+92mKXNTMWdOYYXLD4iM80bK6DLTcCOgz5mXU53 ro6ny58lepRSVQJBSERTN1mFsbu1dbMV8C7ai1VCLLj41+McJgeoWws81et4bKGd0IM4dNakTTHDa UpM0pAn06LFlQYsoiceCcQ==; In-Reply-To: <86il0pd8da.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 10 Apr 2024 09:45:49 +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:283042 Archived-At: > From: Juri Linkov > Cc: rudalics@gmx.at, 69983@debbugs.gnu.org > Date: Wed, 10 Apr 2024 09:45:49 +0300 > > >> > Why does adding a new feature require changes in existing features, > >> > let alone such basic features as warnings.el? Can't we introduce the > >> > category and leave warnings.el, flymake.el, and others alone? I don't > >> > want to make unsolicited changes in those other places, because that > >> > runs the risk of disturbing people's arrangements of windows and their > >> > habits as to where the various windows pop up. > >> > >> This is part of continuing development to improve > >> window handling for users of horizontally split windows. > > > > I don't think I understand how category is related to horizontally > > split windows, please explain. We are still in the context of > > bug#69983 and its Subject, aren't we? > > > > If there are some problems related to horizontally split windows that > > interfere with showing warnings, please describe them. > > The function 'display-warning' has the argument 'buffer-name'. > This means it's impossible to match the buffer name in > 'display-buffer-alist', because the buffer name can be anything. > Therefore the 'category' should be added to the 'display-buffer' > call in 'display-warning'. > > Currently the warning buffer is displayed in a random place > in horizontally split windows. The change is needed to display it > in the consistent place. This change is accompanied with adding > the category for the case if someone don't like this change > (very unlikely) and wants to revert it to display the buffer > in a random place. It will be possible to customize this > by using the category in 'display-buffer-alist'. First, as Martin says, the place is never "random". 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. In any case, if you are suggesting to change the "random" place where warnings are displayed, we should first discuss that, because your assertion that no one will dislike the change sounds very much like famous last words to me, so to speak ;-)