From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23574@debbugs.gnu.org, john.b.mastro@gmail.com,
cwoodbury@azavea.com, npostavs@users.sourceforge.net
Subject: bug#23574: 24.5; Overzealous underlining in emacs-nox
Date: Fri, 10 Jun 2016 09:16:02 +0200 [thread overview]
Message-ID: <575A6932.70908@gmx.at> (raw)
In-Reply-To: <83bn3ar1k3.fsf@gnu.org>
>> OK. But with my property list approach a once calculated bitmap would
>> have simply overridden the face of the iterator object.
>
> Your suggestion included a function, which could well return different
> values on each call.
>
> And creating new faces from arbitrary sets of attributes is no fun,
> either.
OK. I was not fond of my proposal anyway.
>> Suppose a user wants to use the same background for all spaces at the
>> ends of all lines of a buffer regardless of "the last face used on the
>> line". How would she specify that?
>
> By putting the proper face property on the newline.
Which gets me back to my initial concern: If our user does that eagerly
for the entire buffer, the overhead might be non-negligible. A more
lazy solution would require to hook into ‘pre-redisplay-functions’ or
something the like in order to know which lines get displayed. Would
‘pre-redisplay-functions’ be a suitable place for that?
martin
A loosely related question: Does for R2L text row->pixel_width for each
glyph row indicate the width of that row occupied by text as it does for
L2R text? Suppose we have a L2R line with dots indicating the empty
space at the end of that line:
TTTTTTTTTTTTT....
R2L this line would appear as
....TTTTTTTTTTTTT
Would these two lines have the same row->pixel_width? Or, would the
length of the stretch glyph added at the left of the R2L line be that of
‘window-text-width’ minus row->pixel_width?
next prev parent reply other threads:[~2016-06-10 7:16 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
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 [this message]
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=575A6932.70908@gmx.at \
--to=rudalics@gmx.at \
--cc=23574@debbugs.gnu.org \
--cc=cwoodbury@azavea.com \
--cc=eliz@gnu.org \
--cc=john.b.mastro@gmail.com \
--cc=npostavs@users.sourceforge.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).