From: Eli Zaretskii <eliz@gnu.org>
To: Vasilij Schneidermann <v.schneidermann@gmail.com>
Cc: 21500@debbugs.gnu.org
Subject: bug#21500: 24.5; Graphical glitch with display property lines in GUI Emacs
Date: Sat, 26 Sep 2015 14:02:49 +0300 [thread overview]
Message-ID: <83612xh292.fsf@gnu.org> (raw)
In-Reply-To: <20150926105643.GB577@odonien.lan>
> Date: Sat, 26 Sep 2015 12:56:43 +0200
> From: Vasilij Schneidermann <v.schneidermann@gmail.com>
> Cc: 21500@debbugs.gnu.org
>
> > I'm not sure why would you need to use :distant-foreground, but maybe
> > your actual situation is more complicated than the test case you
> > presented in this bug report. With that test case, if I modify the
> > face definition like this:
> >
> > (defface my-line
> > '((((type graphic)) :background "yellow")
> > (((type tty)) :inherit font-lock-comment-face :underline t))
> > "Line face")
> >
> > I see the line in question all the time. Is this what you want?
>
> Well, that works, but it does get rid of the line alltogether, so that's
> hardly a solution.
Is the below better?
(defface my-line
'((((type graphic))
:inherit font-lock-comment-face
:strike-through t
:background "yellow")
(((type tty)) :inherit font-lock-comment-face :underline t))
"Line face")
next prev parent reply other threads:[~2015-09-26 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 19:37 bug#21500: 24.5; Graphical glitch with display property lines in GUI Emacs Vasilij Schneidermann
2015-09-16 20:12 ` Eli Zaretskii
[not found] ` <20150916203402.GA3145@odonien.fritz.box>
2015-09-17 4:57 ` Eli Zaretskii
2015-09-17 6:34 ` Vasilij Schneidermann
2015-09-17 7:05 ` Eli Zaretskii
2015-09-26 8:14 ` Eli Zaretskii
2015-09-26 9:35 ` Vasilij Schneidermann
2015-09-26 10:04 ` Eli Zaretskii
2015-09-26 10:56 ` Vasilij Schneidermann
2015-09-26 11:02 ` Eli Zaretskii [this message]
2015-09-26 12:17 ` Vasilij Schneidermann
2015-09-26 12:14 ` Johan Bockgård
2015-09-26 12:22 ` Vasilij Schneidermann
2015-09-26 13:33 ` 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=83612xh292.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21500@debbugs.gnu.org \
--cc=v.schneidermann@gmail.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 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).