unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: "29805@debbugs.gnu.org" <29805@debbugs.gnu.org>
Subject: bug#29805: [External] : bug#29805: 27.0; doc of `tooltip-resize-echo-area'
Date: Sat, 23 Oct 2021 18:51:29 +0000	[thread overview]
Message-ID: <SJ0PR10MB54886EC39266675AF74036DBF3819@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83y26j4ns2.fsf@gnu.org>

> What is unclear about it?  Drew thinks the doc string should say
> something about stand-alone minibuffer frames, but only Drew can
> explain why.  The doc string talks specifically about the echo-area,
> and about the situation where tooltips are shown in the echo-area; it
> says nothing about minibuffers or minibuffer-only frames.

Yes, it's about the echo area - only; not minibuffers.

As both I and Martin pointed out, resizing the echo area
means resizing the minibuffer area - same real estate.

The doc says that the echo area gets resized.  That
effect doesn't occur with a "minibuffer-only" frame.
The doc would be clearer if it said so.

Such a frame is as much "echo-area-only" as it is
"minibuffer-only".  A standalone "minibuffer" frame
also manifests the echo area - it's a frame for the
minibuffer AND the echo area.

Doc that tells you the echo area gets resized to show
all of the message text should also tell you that this
doesn't apply - the ECHO AREA is not resized - if the
echo area is the only thing in its frame (a so-called
minibuffer-only, or standalone-minibuffer, frame).

Saying that the doc shouldn't be fixed because it's
about the echo area and not about the minibuffer is
a deflection.  No one is saying that it's about the
minibuffer.

It's a minor bug.  But it should at least be obvious
what the (doc) problem is.





  reply	other threads:[~2021-10-23 18:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 22:06 bug#29805: 27.0; doc of `tooltip-resize-echo-area' Drew Adams
2017-12-22 17:57 ` martin rudalics
2017-12-22 18:44   ` Drew Adams
2017-12-23  8:33     ` martin rudalics
2017-12-23 15:20       ` Drew Adams
2017-12-23 19:07         ` martin rudalics
2021-10-23 17:48           ` Stefan Kangas
2021-10-23 18:08             ` Eli Zaretskii
2021-10-23 18:51               ` Drew Adams [this message]
2021-10-23 19:23                 ` bug#29805: [External] : " Eli Zaretskii
2021-10-23 19:50                   ` Drew Adams
2021-10-24  5:52                     ` Eli Zaretskii
2021-10-24 20:45                       ` Drew Adams

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=SJ0PR10MB54886EC39266675AF74036DBF3819@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=29805@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefan@marxist.se \
    /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).