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 15:43:52 -0400 [thread overview]
Message-ID: <c9739f3c-46ff-87d5-2399-7420e1846adc@live.com> (raw)
In-Reply-To: <83wp90g86d.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]
On 2017-05-28 14:14, Eli Zaretskii wrote:> There's a string there, so those properties are processed when the
> display engine traverses the string characters.
Thanks. Understood.
>> Could the same thing happen here?
>
> No, because there's no string. There's just buffer text and nothing
> else.
>
> Maybe we could extend the line-prefix property to support left-fringe
> and right-fringe specs.
Hey, it works!
(insert (propertize "AA" 'line-prefix (propertize "_" 'display '(left-fringe right-arrow))))
:)
Anything bad with this?
>>> 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.
>
> Can you show a simple example where having 5K overlays in a buffer
> cause significant slowdown? I mean, just having 5K overlays, without
> any additional bells and whistles. What exactly is slowed down?
My mode uses overlays for other purposes, and this slows all of it down.
Thanks for your time and answers :)
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-05-28 19:43 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
2017-05-28 18:14 ` Eli Zaretskii
2017-05-28 19:43 ` Clément Pit--Claudel [this message]
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
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=c9739f3c-46ff-87d5-2399-7420e1846adc@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 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).