From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 6253@debbugs.gnu.org
Subject: bug#6253: Please resize mini-buffer for queries even if resize-mini-windows is nil
Date: Sun, 23 May 2010 15:49:52 +0200 [thread overview]
Message-ID: <AANLkTik7faJoQkwnShrYKLbYbI3YUYNOIjSWHMAxjG8h@mail.gmail.com> (raw)
In-Reply-To: <jwv1vd2hh17.fsf-monnier+emacs@gnu.org>
On Sun, May 23, 2010 at 3:43 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> Otherwise you just see the last line of a multiple line query prompt.
>
> Hmm... IIUC when the user sets resize-mini-windows to nil, that's
> because she doesn't want this resizing.
> And multiline prompts are a problem (in cases where resizing is simply
> impossible, for example) in any case. So I think the right thing to do
> is to report the "multiline prompts" as bugs.
I think what the user normally want is to avoid messages that resizes
the miniwindow. I guess most users want to see the whole multiline
prompt.
Why not distinguish between those cases? Maybe a new value for
resize-mini-windows.
With regards to multiline prompts please remember that a "short"
prompt may wrap because it includes something that is long. That could
for example be the case when the prompt includes a file path. So
beeing able to always resize the mini window is useful whatever we do.
next prev parent reply other threads:[~2010-05-23 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 11:46 bug#6253: Please resize mini-buffer for queries even if resize-mini-windows is nil Lennart Borgman
2010-05-23 13:43 ` Stefan Monnier
2010-05-23 13:49 ` Lennart Borgman [this message]
2010-05-23 14:10 ` bug#6253: Please resize mini-buffer for queries even if Stefan Monnier
2010-05-23 22:24 ` Lennart Borgman
2012-04-11 11:13 ` Lars Magne Ingebrigtsen
2012-04-11 12:56 ` Stefan Monnier
2019-06-27 17:12 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTik7faJoQkwnShrYKLbYbI3YUYNOIjSWHMAxjG8h@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=6253@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.