From: martin rudalics <rudalics@gmx.at>
To: Sean Devlin <spd@toadstyle.org>
Cc: 44933@debbugs.gnu.org
Subject: bug#44933: 27.1; Ephemeral frame selection shrinks minibuffer
Date: Mon, 14 Dec 2020 16:47:06 +0100 [thread overview]
Message-ID: <f134366e-ee32-780c-97f6-2c999db83f6f@gmx.at> (raw)
In-Reply-To: <C27524EF-2355-461E-BD45-A4188F5366B9@toadstyle.org>
> Hmm, it seems to show up on the web site:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44933#35. Maybe it is
> getting filtered out somewhere due to size or file extension or
> something?
The attachment shows up in the source text but Thunderbird refuses to
mention or show it here. Emacs has also problems showing it, some lines
are over 4000 characters wide. I have no idea what makes these
backtraces behave so unbridled. Maybe setting `backtrace-line-length'
to something like 80 would help.
Now the basic problem is that I can see only one
'window--resize-root-window-vertically' call and I'd like to see at
least the one where that minibuffer window was enlarged before. So
please try to either set `backtrace-line-length' or do not call
'backtrace' at all when logging and in
'window--resize-root-window-vertically' just before it says
;; Return the possibly adjusted DELTA.
add a line putting into the log the values of 'delta' and 'pixel-delta'
and in 'window--resize-mini-window' just before it says
(unless (zerop delta)
add a line putting into the log the value of 'delta'. Maybe then we can
tell more.
BTW from
window--resize-root-window-vertically(#<window 3 on *redisplay-minibuffer-log*> 70 t)
I conclude that the minibuffer window that gets resized is on a frame
with only one other window - the one showing *redisplay-minibuffer-log*
- right?
Thanks, martin
prev parent reply other threads:[~2020-12-14 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 21:21 bug#44933: 27.1; Ephemeral frame selection shrinks minibuffer Sean Devlin
2020-11-29 8:22 ` martin rudalics
2020-11-29 15:43 ` Sean Devlin
2020-11-30 9:04 ` martin rudalics
2020-11-30 19:32 ` Sean Devlin
2020-12-01 9:33 ` martin rudalics
2020-12-01 20:32 ` Sean Devlin
2020-12-02 7:45 ` martin rudalics
2020-12-02 7:52 ` martin rudalics
2020-12-02 18:24 ` Sean Devlin
2020-12-12 20:23 ` Sean Devlin
2020-12-13 7:26 ` martin rudalics
2020-12-13 16:10 ` Sean Devlin
2020-12-14 15:47 ` martin rudalics [this message]
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=f134366e-ee32-780c-97f6-2c999db83f6f@gmx.at \
--to=rudalics@gmx.at \
--cc=44933@debbugs.gnu.org \
--cc=spd@toadstyle.org \
/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).