From: Stephen Berman <stephen.berman@gmx.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 6192@debbugs.gnu.org
Subject: bug#6192: 24.0.50; eldoc-mode: unexpected recentering
Date: Sun, 16 May 2010 12:45:33 +0200 [thread overview]
Message-ID: <87ljbkyvjm.fsf@escher.home> (raw)
In-Reply-To: <4BEFAA20.9000301@gmx.at> (martin rudalics's message of "Sun, 16 May 2010 10:17:36 +0200")
On Sun, 16 May 2010 10:17:36 +0200 martin rudalics <rudalics@gmx.at> wrote:
>> Of course; so can you confirm that you do not see the resizing with -Q
>> and then enabling eldoc mode?
>
> I have tried the trunk with -Q now and can't trigger the resizing any
^^^
> more, neither with a hook nor when setting it manually.
^^^^
It's not that the bug is no longer reliably reproducible; rather, you do
confirm my observation that the resizing happens iff eldoc-mode is
enabled in the user init file. So what difference between running a
hook there and running it later could lead to the bug?
Steve Berman
next prev parent reply other threads:[~2010-05-16 10:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 17:11 bug#6192: 24.0.50; eldoc-mode: unexpected recentering Stephen Berman
2010-05-14 17:49 ` Eli Zaretskii
2010-05-14 18:07 ` Stephen Berman
2010-05-14 21:05 ` Eli Zaretskii
2010-05-14 21:44 ` Stephen Berman
2010-05-15 6:36 ` Eli Zaretskii
2010-05-15 15:40 ` Stephen Berman
2010-05-15 16:44 ` Eli Zaretskii
2010-05-15 17:25 ` Stephen Berman
2010-05-15 17:33 ` Eli Zaretskii
2010-05-15 21:54 ` Stephen Berman
2010-05-15 22:52 ` martin rudalics
2010-05-16 3:07 ` Eli Zaretskii
2010-05-16 8:18 ` martin rudalics
2010-05-16 17:14 ` Eli Zaretskii
2010-05-15 16:53 ` martin rudalics
2010-05-15 17:26 ` Stephen Berman
2010-05-15 19:02 ` martin rudalics
2010-05-15 20:22 ` Eli Zaretskii
2010-05-15 20:47 ` martin rudalics
2010-05-15 21:04 ` Juanma Barranquero
2010-05-15 22:51 ` martin rudalics
2010-05-15 21:14 ` Eli Zaretskii
2010-05-15 22:52 ` martin rudalics
2010-05-15 21:54 ` Stephen Berman
2010-05-15 22:53 ` martin rudalics
2010-05-16 8:17 ` martin rudalics
2010-05-16 10:45 ` Stephen Berman [this message]
2010-05-16 12:35 ` martin rudalics
2010-05-16 13:07 ` Stephen Berman
2010-05-16 18:50 ` martin rudalics
2010-05-16 19:48 ` Stephen Berman
2010-05-17 9:06 ` martin rudalics
2010-05-17 9:47 ` Stephen Berman
2010-05-17 10:21 ` Juanma Barranquero
2010-05-17 10:31 ` Stephen Berman
2010-05-17 14:08 ` Stefan Monnier
2010-05-17 14:43 ` Lennart Borgman
2010-05-17 16:23 ` Juanma Barranquero
2010-05-17 16:33 ` Lennart Borgman
2010-05-17 16:39 ` Juanma Barranquero
2010-05-17 17:53 ` Eli Zaretskii
2010-05-17 18:02 ` Lennart Borgman
2010-05-17 18:30 ` Eli Zaretskii
2010-05-17 18:49 ` Lennart Borgman
2010-05-17 19:27 ` Lennart Borgman
2010-05-17 19:55 ` Stefan Monnier
2010-05-14 21:05 ` Eli Zaretskii
2022-05-05 12:20 ` bug#14520: 24.3; minibuffer resizes when message contains bold or italic text Lars Ingebrigtsen
2022-05-05 12:50 ` Stephen Berman
2022-05-05 13:07 ` Lars Ingebrigtsen
2022-05-05 16:25 ` bug#14520: bug#6192: " Eli Zaretskii
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=87ljbkyvjm.fsf@escher.home \
--to=stephen.berman@gmx.net \
--cc=6192@debbugs.gnu.org \
--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 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).