From: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27103@debbugs.gnu.org
Subject: bug#27103: Should show-trailing-whitespace highlight specified spaces?
Date: Sun, 28 May 2017 13:53:09 -0400 [thread overview]
Message-ID: <c171e3b6-7df3-83b8-e6d5-01d0cd95a28b@live.com> (raw)
In-Reply-To: <83y3tgg9ks.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]
On 2017-05-28 13:44, Eli Zaretskii wrote:
>> And the contents of the buffer would look like this:
>>
>> → (defun …
>> …)
>>
>> → (defun …
>> …)
>
> But this again asks that the display engine could produce 2 different
> display elements out of the same buffer position, which means it would
> need to scan that buffer position twice. Right?
Possibly — I don't think I understand this part well. What happens for before-string properties? Could the same thing happen here?
>> I don't think such a result is currently achievable without overlays (which are not nearly fast enough for my purposes).
>
> Are overlays really so slow that you are prepared to jump through such
> hoops?
Definitely :) I need these markers for a literate-programming buffer where roughly every other line has a marker. On a 10k lines file, overlays are entirely impractical.
(I guess I could lazily add an remove the overlays, but I'm not too excited about reimplementing jit-lock's logic :/)
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-05-28 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 16:47 bug#27103: Should show-trailing-whitespace highlight specified spaces? Clément Pit--Claudel
2017-05-27 18:26 ` Eli Zaretskii
2017-05-27 19:14 ` Clément Pit--Claudel
2017-05-27 19:42 ` Eli Zaretskii
2017-05-27 19:52 ` Clément Pit--Claudel
2017-05-28 16:28 ` Eli Zaretskii
2017-05-28 16:43 ` Clément Pit--Claudel
2017-05-28 17:44 ` Eli Zaretskii
2017-05-28 17:53 ` Clément Pit--Claudel [this message]
2017-05-28 18:14 ` Eli Zaretskii
2017-05-28 19:43 ` Clément Pit--Claudel
2017-05-28 19:51 ` Eli Zaretskii
2017-05-28 20:18 ` Clément Pit--Claudel
2017-05-29 2:30 ` Eli Zaretskii
2017-05-29 2:33 ` Clément Pit--Claudel
2017-05-29 17:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c171e3b6-7df3-83b8-e6d5-01d0cd95a28b@live.com \
--to=clement.pitclaudel@live.com \
--cc=27103@debbugs.gnu.org \
--cc=eliz@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.