unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Juri Linkov <juri@linkov.net>
Cc: martin rudalics <rudalics@gmx.at>,
	63455@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#63455: 30.0.50; display-buffer-in-direction is always resizing
Date: Wed, 24 May 2023 04:48:37 +0200	[thread overview]
Message-ID: <87353m8mwq.fsf@web.de> (raw)
In-Reply-To: <867csy6h2w.fsf@mail.linkov.net> (Juri Linkov's message of "Tue,  23 May 2023 21:25:11 +0300")

Juri Linkov <juri@linkov.net> writes:

> > I always found that naming confusing.  It makes me think of
> > `with-temp-buffer', helper buffers, not of *Help*.  Do you find the
> > naming appropriate, having the use cases in mind?
>
> According to (info "(emacs) Temporary Displays")
> maybe a better name would be "view-buffer" because
> it's intended for non-editable buffers.

Hmm - I think that name sounds a bit too general to me.

I don't know - it's all a bit messy.

`with-output-to-temp-buffer' displays the buffer.  That's also a bit
surprising.

(info "(elisp) Temporary Displays") says:

 -- User Option: temp-buffer-show-function
     If this variable is non-‘nil’, ‘with-output-to-temp-buffer’ calls
     it as a function to do the job of displaying a help buffer.
                                                    ^^^^
The name "temp" is everywhere.  And it is, in the context of buffer
display (in the wider sense), more or less synonymous with "help
buffer" (in the wider sense again).

If it's too late to change all of the related names, maybe we should
describe the naming habits more explicitly so that it is less confusing
and more discoverable.

Michael.





  reply	other threads:[~2023-05-24  2:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  1:06 bug#63455: 30.0.50; display-buffer-in-direction is always resizing Michael Heerdegen
2023-05-12  7:39 ` martin rudalics
2023-05-12 17:16   ` Juri Linkov
2023-05-13  8:56     ` martin rudalics
2023-05-15 17:01       ` Juri Linkov
2023-05-15 18:21         ` Eli Zaretskii
2023-05-16  7:19         ` martin rudalics
2023-05-16 16:35           ` Juri Linkov
2023-05-17 16:56   ` Juri Linkov
2023-05-18  8:29     ` martin rudalics
2023-05-18 15:54       ` Juri Linkov
2023-05-19  7:31         ` martin rudalics
2023-05-19 17:54       ` Juri Linkov
2023-05-20  8:27         ` martin rudalics
2023-05-22 18:03           ` Juri Linkov
2023-05-23  2:30             ` Michael Heerdegen
2023-05-23 18:25               ` Juri Linkov
2023-05-24  2:48                 ` Michael Heerdegen [this message]
2023-05-12 17:11 ` Juri Linkov
2023-05-13  5:29   ` Michael Heerdegen
2023-05-15 17:02     ` 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=87353m8mwq.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=63455@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --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).