From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, 29805@debbugs.gnu.org
Subject: bug#29805: 27.0; doc of `tooltip-resize-echo-area'
Date: Sat, 23 Dec 2017 20:07:42 +0100 [thread overview]
Message-ID: <5A3EA97E.9060501@gmx.at> (raw)
In-Reply-To: <dc7ae3de-0f0e-4e51-a398-f6c905458a21@default>
> This bug is not about whether or when there should or
> should not be resizing. It is about the doc, which
> can (so far) give the impression that this resizing
> affects this real estate even when a standalone frame
> is involved - which it does not, AFAIK.
Any such resizing is governed by the setting of `resize-mini-windows'
and whether the echo area can be resized at all. There are various
reasons why the echo area can't be resized - for example, when the
root window has fixed size, when the echo area occupies the only
window on its frame or when the frame is too small. Maybe there are
more. So the standalone frame case is just one among others.
But this is just my POV of this matter. As should be clear from my
previous remarks in this thread, I apparently do not understand the
use of the echo area for showing tooltips and neither the difference
between echo area and minibuffer. So I'll rather leave this for the
inventor of `tooltip-resize-echo-area' to fix.
martin
next prev parent reply other threads:[~2017-12-23 19:07 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 [this message]
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
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=5A3EA97E.9060501@gmx.at \
--to=rudalics@gmx.at \
--cc=29805@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).