From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: bug#1510: 23.0.60; Info links bleed into mode line
Date: Sun, 7 Dec 2008 13:43:32 -0800 [thread overview]
Message-ID: <000101c958b4$d9c90fc0$0200a8c0@us.oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
emacs -Q
C-h i
Pick a manual, and go to any node that has a menu too long to be
displayed completely.
Menu links seem to cause a blue strike-through line in the mode
line. It seems that a menu link directly underneath the mode line
(hence not visible) has its underline brought forward on top of the
mode line.
C-l removes the strike-through display artifact. Otherwise, it
persists even if you move to a node that has no menu or has a menu
that can be displayed completely.
After clearing the screen this way, if you go to a node with a menu
that can all be displayed, and then you manually shorten the frame so
a menu item is hidden by the mode line, then the strike-through
returns.
See attached screen shots.
In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
of 2008-11-24 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
[-- Attachment #2: bug-emacs-23-info-link-in-mode-line.png --]
[-- Type: image/png, Size: 60770 bytes --]
[-- Attachment #3: bug-emacs-23-info-link-in-mode-line-2.png --]
[-- Type: image/png, Size: 47727 bytes --]
next reply other threads:[~2008-12-07 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4950BEF7.9010508@gnu.org>
2008-12-07 21:43 ` Drew Adams [this message]
2008-12-09 5:41 ` bug#1510: 23.0.60; Info links bleed into mode line jasonr
2008-12-10 1:52 ` Drew Adams
2008-12-22 22:45 ` Drew Adams
2008-12-23 10:40 ` bug#1510: marked as done (23.0.60; Info links bleed into mode line) Emacs bug Tracking System
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='000101c958b4$d9c90fc0$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=1510@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.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 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.