From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 69983@debbugs.gnu.org, juri@linkov.net
Subject: bug#69983: Use category for display-buffer-alist
Date: Thu, 11 Apr 2024 14:03:29 +0300 [thread overview]
Message-ID: <86ttk8tb3y.fsf@gnu.org> (raw)
In-Reply-To: <f3e87f20-d909-419f-b058-a1c960c501d0@gmx.at> (message from martin rudalics on Thu, 11 Apr 2024 11:16:25 +0200)
> Date: Thu, 11 Apr 2024 11:16:25 +0200
> Cc: 69983@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> > 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 ;-)
>
> This part
>
> + '(display-buffer--maybe-at-bottom
> + (window-height . (lambda (window)
> + (fit-window-to-buffer window 10)))
>
> would hard-code a new preference which might cause problems indeed. But
> the subsequent
>
> + (category . warning)))))
>
> would allow users to customize the display of warnings via
> 'display-buffer-alist' and cannot harm otherwise.
I understand, and might even agree. But (a) as I wrote elsewhere in
this thread, I don't think display-buffer-alist should be the
advertised means of controlling display of warnings, and (b) I happen
to think that display-buffer-alist is so complex and arcane that
asking users to use it as the means of customizing such simple
settings is not very user-friendly, to say the least, especially when
we change existing behavior (which is likely to cause users to want to
get the previous behavior back).
This is why I suggested to discuss the proposed new behavior. It is
possible that we will all agree that it is superior to the old one, in
which case the above-mentioned considerations will not apply. But if
not, then the default should reflect what we think most users will
want, and how to implement that takes a back seat.
next prev parent reply other threads:[~2024-04-11 11:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 17:19 bug#69983: Use category for display-buffer-alist Juri Linkov
2024-03-25 9:41 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-25 17:12 ` Juri Linkov
2024-03-26 9:55 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-27 7:15 ` Juri Linkov
2024-03-28 7:47 ` Juri Linkov
2024-03-28 8:23 ` Eli Zaretskii
2024-03-28 17:46 ` Juri Linkov
2024-03-28 9:18 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 17:50 ` Juri Linkov
2024-03-29 8:43 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-29 16:30 ` Juri Linkov
2024-03-30 9:36 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-30 18:22 ` Juri Linkov
2024-04-02 16:52 ` Juri Linkov
2024-04-04 6:16 ` Juri Linkov
2024-04-05 16:47 ` Juri Linkov
2024-04-06 18:42 ` Juri Linkov
2024-04-07 8:22 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 6:30 ` Juri Linkov
2024-04-09 7:09 ` Eli Zaretskii
2024-04-09 16:34 ` Juri Linkov
2024-04-09 18:28 ` Eli Zaretskii
2024-04-10 6:45 ` Juri Linkov
2024-04-10 8:47 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-10 11:07 ` Eli Zaretskii
2024-04-10 17:49 ` Juri Linkov
2024-04-10 18:13 ` Eli Zaretskii
2024-04-11 6:31 ` Juri Linkov
2024-04-11 7:40 ` Eli Zaretskii
2024-04-12 6:37 ` Juri Linkov
2024-04-12 7:05 ` Eli Zaretskii
2024-04-12 16:50 ` Juri Linkov
2024-04-12 18:27 ` Eli Zaretskii
2024-04-13 18:49 ` Juri Linkov
2024-04-13 19:03 ` Eli Zaretskii
2024-04-14 16:04 ` Juri Linkov
2024-04-18 14:30 ` Eli Zaretskii
2024-04-18 17:16 ` Juri Linkov
2024-04-18 17:56 ` Eli Zaretskii
2024-04-19 6:24 ` Juri Linkov
2024-04-19 6:28 ` Juri Linkov
2024-04-19 7:19 ` Eli Zaretskii
2024-04-19 16:17 ` Juri Linkov
2024-04-20 12:08 ` Eli Zaretskii
2024-04-21 6:52 ` Juri Linkov
2024-04-21 9:13 ` Eli Zaretskii
2024-04-22 6:50 ` Juri Linkov
2024-04-19 7:19 ` Eli Zaretskii
2024-04-11 9:16 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-11 11:03 ` Eli Zaretskii [this message]
2024-04-24 16:46 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ttk8tb3y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69983@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).