all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <1510@emacsbugs.donarmstrong.com>, <jasonr@f2s.com>
Subject: bug#1510: 23.0.60; Info links bleed into mode line
Date: Mon, 22 Dec 2008 14:45:28 -0800	[thread overview]
Message-ID: <001401c96486$fd816240$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <008501c95a69$e87ecda0$0200a8c0@us.oracle.com>

In this build, this seems to be fixed. Thx - Drew

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-12-19 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'


> From: Drew Adams Sent: Tuesday, December 09, 2008 5:52 PM
> > > 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.
> > 
> > I can't reproduce this with the current CVS trunk. It is 
> > possible that a change
> > I checked in last week fixed this, or maybe it is specific to 
> > your environment
> > such as the specific fonts being used. Can you please let us 
> > know if the bug is
> > still there after you next update Emacs.
> 
> OK, thanks for checking. I'll try to remember to check again 
> with a more recent build. - Drew







  reply	other threads:[~2008-12-22 22:45 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 ` bug#1510: 23.0.60; Info links bleed into mode line Drew Adams
2008-12-09  5:41   ` jasonr
2008-12-10  1:52     ` Drew Adams
2008-12-22 22:45       ` Drew Adams [this message]
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='001401c96486$fd816240$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=1510@emacsbugs.donarmstrong.com \
    --cc=jasonr@f2s.com \
    /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.