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>
Cc: "stefan@marxist.se" <stefan@marxist.se>,
	"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 19:50:27 +0000	[thread overview]
Message-ID: <SJ0PR10MB548802DA1CDBA232A723FC02F3819@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83pmrv4kam.fsf@gnu.org>

> > A standalone "minibuffer" frame also manifests the
> > echo area
> 
> No, it doesn't.  It serves as the minibuffer window,
> but it isn't the echo-area.

(No one said it "is" the echo area.  And no one but
you has said that such a frame is, or "serves as",
a window.)

Where do you think the echo area is manifested, if
you have a minibuffer-only frame and no other frame
has a minibuffer?

Bingo - that's what we're talking about.  That's the
(most common, and probably the only) use case of a
standalone minibuffer frame - it provides THE
mini-window.

The echo area always uses the same real estate as a
minibuffer.  If the only minibuffer is standalone
then - guess what - that's where the echo are is, in
that standalone "minibuffer" frame.

> > 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).
> 
> It makes no sense to talk about resizing the minibuffer-only frame,
> because it has more than one line to begin with.

Nonsense.  It has whatever number of lines it's
configured to have.  See `minibuffer-frame-alist'.





  reply	other threads:[~2021-10-23 19:50 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               ` bug#29805: [External] : " Drew Adams
2021-10-23 19:23                 ` Eli Zaretskii
2021-10-23 19:50                   ` Drew Adams [this message]
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=SJ0PR10MB548802DA1CDBA232A723FC02F3819@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).