From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
ndame <emacsuser@freemail.hu>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Shouldn't emacs print long lists with newlines?
Date: Wed, 28 Aug 2019 13:23:53 -0400 [thread overview]
Message-ID: <jwv7e6xcioi.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <9535bbe5-cb70-f2be-3d17-010da8a4be1b@gmx.at> (martin rudalics's message of "Wed, 7 Aug 2019 14:04:33 +0200")
>> [ My minibuffer is exactly 1-line tall (and it's a separate frame, so
>> Emacs is not allowed to grow it)
> Since you can now customize 'resize-mini-frames' this restriction no
> longer applies (at least not as stated here).
FWIW, resize-mini-frames doesn't work very well for me:
- at startup it resizes the frame to a one-line frame of maybe 10-20
chars long, which is oddly short. The length is updated on the fly,
but I find this a bit annoying. Nothing too serious tho.
- I have my minibuffer frame at the bottom of the screen. When it grows
to two or more lines, it correctly moves up. But when it shrinks back
to a single line, it doesn't move back down, so it ends up "near" the
bottom rather than at the bottom.
The second problem is probably partly linked to the window-manager, but
I've found size-varying windows at the bottom of the screen to be poorly
handled under X11 in general (not only with the window-manager
I'm using), so I think I'd have to move my minibuffer-only frame to the
top of the screen to avoid those problem :-(
>> , so spreading the output on several
>> lines is not always a good solution. ]
So this still holds :-(
Stefan
next prev parent reply other threads:[~2019-08-28 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 20:05 Shouldn't emacs print long lists with newlines? ndame
2019-08-07 7:05 ` Michael Heerdegen
2019-08-07 10:51 ` Stefan Monnier
2019-08-07 12:04 ` martin rudalics
2019-08-28 17:23 ` Stefan Monnier [this message]
2019-08-29 7:46 ` martin rudalics
2019-08-07 12:43 ` ndame
2019-08-07 14:28 ` Michael Heerdegen
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=jwv7e6xcioi.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=emacsuser@freemail.hu \
--cc=michael_heerdegen@web.de \
--cc=rudalics@gmx.at \
/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.