unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 09:33:48 +0100	[thread overview]
Message-ID: <5A3E14EC.3010809@gmx.at> (raw)
In-Reply-To: <7614565b-94d6-40fe-a3d1-cf51235a21bc@default>

 >> So the question to be
 >> answered first is: Do we ever want to fit stand-alone minibuffer
 >> frames to their buffers?
 >
 > Please don't bother for me, anyway. ;-)

If we don't want to, the entire remainder of this discussion is moot.

 > The bug report was really to suggest that such doc about
 > resizing the space for the minibuffer / echo area should
 > not lead people to believe that such resizing resizes a
 > frame.  It applies only to a window in a frame that is
 > not minibuffer-only (AFAICT), so that should be made clear.

Resizing the echo area when showing a tooltip is just a special case
of resizing the minibuffer window so any reasonable discussion of the
former would have to start with the latter.

 >> 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.
 >
 > 1. No idea why we now have it.
 > 2. The doc string is wrong to refer to `tooltip-use-echo-area'.

Which doc string does (2)?

 >> Resolved that, we should probably then also say that
 >> `tooltip-resize-echo-area' has effect iff `resize-mini-windows' is
 >> non-nil.
 >
 > And why isn't `resize-mini-windows' enough?  Is this about
 > resizing ONLY the echo area and not the minibuffer?  (Does
 > that even make sense?)
 >
 > It's all unclear to me.

To me too.  I have no idea why we (or at least an Emacs user) should
ever have to distinguish betweeen echo area and minibuffer.  There's
no practical need for that.

martin





  reply	other threads:[~2017-12-23  8:33 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 [this message]
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=5A3E14EC.3010809@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).