From: John Mastro <john.b.mastro@gmail.com>
To: 23574@debbugs.gnu.org
Cc: Colin Woodbury <cwoodbury@azavea.com>
Subject: bug#23574: 24.5; Overzealous underlining in emacs-nox
Date: Sat, 4 Jun 2016 14:37:28 -0700 [thread overview]
Message-ID: <CAOj2CQQ7AXQr5R7s4H=ARCZ8i=hTKkn1M_pcMUEueD+6MS4vvA@mail.gmail.com> (raw)
In-Reply-To: <83d1nxudrb.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> wrote:
>> Thanks for the response, Eli. If it's not a bug in terminal emacs,
>> then why do GUI emacs and terminal emacs display different things?
>> Note from the images that the empty space in GUI is _not_ given the
>> same overlay/face as the text.
>
> If you show me some Lisp which produces these different effects in X
> and non-X sessions, I could try looking for the reason. All I've seen
> is a screenshot, from which I deduced (perhaps incorrectly) what was
> done to produce it.
Here's an example shows the effect Colin is seeing:
(let (beg end ov)
(defface example-underline-face
'((t :underline t))
"Example face with underlining")
(goto-char (point-max))
(newline)
(setq beg (point))
(insert " foo\n bar\n")
(setq end (point))
(setq ov (make-overlay beg end))
(overlay-put ov 'face 'example-underline-face))
The result is the same with text properties instead of an overlay:
(progn
(defface example-underline-face
'((t :underline t))
"Example face with underlining")
(goto-char (point-max))
(newline)
(insert (propertize " foo\n bar\n"
'font-lock-face
'example-underline-face)))
In a graphical frame, the underline only extends one character past the
visible text (this one extra character presumably being the newline).
However, in a text frame the underline extends all the way to the end of
the window.
John
next prev parent reply other threads:[~2016-06-04 21:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 17:03 bug#23574: 24.5; Overzealous underlining in emacs-nox Colin Woodbury
2016-05-30 15:04 ` Colin Woodbury
2016-06-04 7:48 ` Eli Zaretskii
[not found] ` <CAHuwsfihHJ8WHwmHvMDF7Ynns4YOJSKEEbjhpbYrw0V=5aYXEQ@mail.gmail.com>
2016-06-04 16:20 ` Eli Zaretskii
2016-06-04 21:37 ` John Mastro [this message]
2016-06-05 15:54 ` Eli Zaretskii
2016-06-05 17:05 ` Noam Postavsky
2016-06-05 17:56 ` Eli Zaretskii
2016-06-05 18:20 ` Colin Woodbury
2016-06-05 18:36 ` Eli Zaretskii
2016-06-05 19:13 ` Noam Postavsky
2016-06-06 2:27 ` Eli Zaretskii
2016-06-06 11:42 ` Noam Postavsky
2016-06-06 15:04 ` Eli Zaretskii
2016-06-06 16:54 ` martin rudalics
2016-06-06 18:25 ` Colin Woodbury
2016-06-06 19:18 ` Eli Zaretskii
2016-06-07 0:18 ` Noam Postavsky
2016-06-07 15:55 ` Eli Zaretskii
2016-06-08 2:52 ` Noam Postavsky
2016-06-06 18:55 ` Eli Zaretskii
2016-06-07 9:10 ` martin rudalics
2016-06-07 15:50 ` Eli Zaretskii
2016-06-08 6:33 ` martin rudalics
2016-06-08 17:05 ` Eli Zaretskii
2016-06-09 8:38 ` martin rudalics
2016-06-09 12:26 ` Eli Zaretskii
2016-06-10 7:16 ` martin rudalics
2016-06-10 8:10 ` Eli Zaretskii
2016-06-10 8:24 ` martin rudalics
2016-06-10 9:50 ` Eli Zaretskii
2016-06-10 13:59 ` martin rudalics
2016-06-10 14:24 ` Eli Zaretskii
2019-10-21 11:49 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-08 5:32 ` Lars Ingebrigtsen
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='CAOj2CQQ7AXQr5R7s4H=ARCZ8i=hTKkn1M_pcMUEueD+6MS4vvA@mail.gmail.com' \
--to=john.b.mastro@gmail.com \
--cc=23574@debbugs.gnu.org \
--cc=cwoodbury@azavea.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).