From: martin rudalics <rudalics@gmx.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45688@debbugs.gnu.org
Subject: bug#45688: 28.0.50; New action for display-buffer?
Date: Thu, 7 Jan 2021 17:54:51 +0100 [thread overview]
Message-ID: <140175de-6194-bab4-a66e-4e2b8ab85034@gmx.at> (raw)
In-Reply-To: <87k0so3fxb.fsf@gnus.org>
> By the way, the example in the Emacs manual is this:
>
> (customize-set-variable
> 'display-buffer-alist
> '("\\*scratch\\*" (display-buffer-same-window)))
>
> Which isn't an alist?
Darn. No wonder that people complain. Maybe we should use one of the
examples from the Zen of Buffer Display. In either case this is for
Emacs 27.2!
martin
next prev parent reply other threads:[~2021-01-07 16:54 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 12:02 bug#45688: 28.0.50; New action for display-buffer? Lars Ingebrigtsen
2021-01-06 13:36 ` martin rudalics
2021-01-06 14:09 ` Lars Ingebrigtsen
2021-01-06 15:52 ` martin rudalics
2021-01-07 11:45 ` Lars Ingebrigtsen
2021-01-07 13:18 ` martin rudalics
2021-01-07 14:47 ` Lars Ingebrigtsen
2021-01-07 15:17 ` martin rudalics
2021-01-07 15:35 ` martin rudalics
2021-01-07 15:49 ` Lars Ingebrigtsen
2021-01-07 16:54 ` martin rudalics [this message]
2021-01-06 15:45 ` Eli Zaretskii
2021-01-06 17:20 ` Lars Ingebrigtsen
2021-01-06 18:17 ` Eli Zaretskii
2021-01-07 11:40 ` Lars Ingebrigtsen
2021-01-07 13:17 ` martin rudalics
2021-01-07 15:39 ` Lars Ingebrigtsen
2021-01-07 16:54 ` martin rudalics
2021-01-10 11:24 ` Lars Ingebrigtsen
2021-01-10 16:05 ` martin rudalics
2021-01-10 16:14 ` martin rudalics
2021-01-11 14:43 ` Lars Ingebrigtsen
2021-01-11 18:23 ` martin rudalics
2021-01-11 18:55 ` martin rudalics
2021-01-19 3:20 ` Lars Ingebrigtsen
2021-01-11 19:05 ` Lars Ingebrigtsen
2021-01-12 9:06 ` martin rudalics
2021-01-19 3:26 ` Lars Ingebrigtsen
2021-01-20 8:08 ` martin rudalics
2021-01-20 16:34 ` Lars Ingebrigtsen
2021-01-20 17:11 ` martin rudalics
2021-01-19 17:50 ` Juri Linkov
2021-01-20 8:09 ` martin rudalics
2021-01-20 21:45 ` Juri Linkov
2021-01-25 19:03 ` martin rudalics
2021-01-25 20:08 ` Juri Linkov
2021-01-26 15:57 ` martin rudalics
2021-01-27 9:38 ` Juri Linkov
2021-01-28 9:40 ` martin rudalics
2021-10-03 18:12 ` Juri Linkov
2021-10-04 8:28 ` martin rudalics
2021-10-04 17:31 ` Juri Linkov
2021-10-05 6:43 ` Lars Ingebrigtsen
2021-10-05 8:10 ` martin rudalics
2021-10-05 16:49 ` Juri Linkov
2021-10-06 7:41 ` martin rudalics
2021-10-06 17:45 ` Juri Linkov
2021-10-13 8:36 ` martin rudalics
2021-01-11 14:45 ` Lars Ingebrigtsen
2021-01-07 18:43 ` Juri Linkov
2021-01-08 8:31 ` martin rudalics
2021-01-10 11:26 ` Lars Ingebrigtsen
2021-01-12 18:36 ` Juri Linkov
2021-01-19 17:52 ` Juri Linkov
2021-01-25 20:10 ` Juri Linkov
2021-01-26 15:57 ` martin rudalics
2021-01-27 9:35 ` Juri Linkov
2021-01-28 9:40 ` martin rudalics
2021-01-28 18:46 ` Juri Linkov
2021-01-29 7:51 ` martin rudalics
2021-01-06 17:41 ` Juri Linkov
2021-01-06 18:28 ` Drew Adams
2021-01-06 18:47 ` martin rudalics
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=140175de-6194-bab4-a66e-4e2b8ab85034@gmx.at \
--to=rudalics@gmx.at \
--cc=45688@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).