unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 6192@debbugs.gnu.org
Subject: bug#6192: 24.0.50; eldoc-mode: unexpected recentering
Date: Mon, 17 May 2010 10:08:49 -0400	[thread overview]
Message-ID: <jwvmxvywryp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874oi6oo6f.fsf@escher.home> (Stephen Berman's message of "Mon, 17 May 2010 11:47:04 +0200")

> In short, this bug now boils down to this: the echo area resizes with
> certain fonts (including DejaVu Sans Mono) when it displays a message
> that includes bold face.  Whether this is a bug in Emacs or the
> problematic fonts, I don't know.

To summarize this long thread, IIUC we have three separate problems:
- in some cases, a minibuffer message with bold text causes
  unexpected/unneeded minibuffer resizing.  Most likely those fonts
  somehow end up with a height just a tiny pixel taller.  Maybe we
  should change the minibuffer resizing such that it only resizes if the
  extra height needed is more than some threshold number of pixels (1
  or 2).
- eldoc can cause undesired minibuffer resizing.  That can probably still
  happen even when we fix the previous problem, depending on face
  settings and/or length of eldoc data.  So maybe eldoc should come with
  a config var for how many max lines of echo-area we're willing to
  devote to it.  If set to 1 it will prevent any resizing and fix the
  OP's problem regardless of whether the previous problem is fixed.
- minibuffer auto-resize can trigger an undesirable recentering.
  I'm not sure we can do much about that, tho, since it seems to only
  occur in cases where the resizing ends up "eating" the area used by
  point, so some scrolling is necessary.


        Stefan





  parent reply	other threads:[~2010-05-17 14:08 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
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 [this message]
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=jwvmxvywryp.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=6192@debbugs.gnu.org \
    --cc=stephen.berman@gmx.net \
    /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).