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: Fri, 22 Dec 2017 18:57:09 +0100 [thread overview]
Message-ID: <5A3D4775.2010700@gmx.at> (raw)
In-Reply-To: <d9b8c871-9c31-4360-af35-04ee83db4f62@default>
> In any case, it seems to have no effect, AFAICT, on a standalone
> minibuffer frame (i.e., on an echo area in such a frame). The doc says
> nothing about this..
I believe we also nowhere say that we do not resize minibuffer/echo
areas on stand-alone minibuffer frames. So the question to be
answered first is: Do we ever want to fit stand-alone minibuffer
frames to their buffers? If so, then we can decide whether we want
`tooltip-resize-echo-area' to affect resizing stand-alone minibuffer
frames as well and probably also whether showing a tooltip should
autoraise the minibuffer frame.
But the first question that comes to my mind is why we now have the
option `tooltip-resize-echo-area' which, according to its doc-string
"has effect only on GUI frames" while in Emacs 24.1 we have declared
`tooltip-use-echo-area' obsolete and suggested to disable tooltips
instead. Resolved that, we should probably then also say that
`tooltip-resize-echo-area' has effect iff `resize-mini-windows' is
non-nil.
martin
next prev parent reply other threads:[~2017-12-22 17:57 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 [this message]
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
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=5A3D4775.2010700@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).