From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, jaygkamat@gmail.com
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: rmsbolt.el [Was: Colorful line numbers]
Date: Fri, 22 Jul 2022 17:30:46 +0100 [thread overview]
Message-ID: <CALDnm50Ob0zQoxDN9bREGHwxYb6n_k7HEObq+FaXdiSGGoAQzg@mail.gmail.com> (raw)
In-Reply-To: <83k085jgxr.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1366 bytes --]
On Fri, Jul 22, 2022 at 4:38 PM Eli Zaretskii <eliz@gnu.org> wrote:
> How else would you know where such re-scanning is needed? An Emacs
> command could change buffer text in several places and in different
> ways, and you must ensure all the characters of a line have the
> correct properties.
>
Depends on the application. Each application just sets properties where
and when it sees fit. It can keep track of where it set them using
markers,
for example. Also many commands such as movement don't change text.
Aaanyway, I think I'm happy with the current implementation that _doesn't_
use line numbers at all. I think this discussion has been productive (to
some
degree). If I ever need this again (or someone else, like Dmitry), I'll be
sure
to ping here again.
For now, my itch has been scratched with a less complicated
back-scratcher. And what a scratch! I attach an animated gif, which
incidentally shows the how the rmsbolt.el package I was describing
earlier works.
Changing the subject completely, I wonder if there's any interest in
adding rmsbolt.el to GNU Elpa or even to core. It's not just for C/C++,
it works for a bunch of languages.
https://gitlab.com/jgkamat/rmsbolt
Apologies if it's old news and everyone's been using this, but
it's the best package I've seen appear in some time.
João Távora
[-- Attachment #1.2: Type: text/html, Size: 2073 bytes --]
[-- Attachment #2: rmsbolt-is-great.gif --]
[-- Type: image/gif, Size: 200311 bytes --]
next prev parent reply other threads:[~2022-07-22 16:30 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 7:50 Colorful line numbers João Távora
2022-07-22 11:00 ` Eli Zaretskii
2022-07-22 11:29 ` João Távora
2022-07-22 11:42 ` Eli Zaretskii
2022-07-22 12:02 ` João Távora
2022-07-22 13:27 ` Eli Zaretskii
2022-07-22 13:53 ` João Távora
2022-07-22 14:33 ` Eli Zaretskii
2022-07-22 15:10 ` João Távora
2022-07-22 15:38 ` Eli Zaretskii
2022-07-22 16:30 ` João Távora [this message]
2022-07-22 19:53 ` rmsbolt.el [Was: Colorful line numbers] Stefan Monnier
2022-07-23 6:13 ` Eli Zaretskii
2022-07-23 9:35 ` João Távora
2022-07-23 10:25 ` Eli Zaretskii
2022-07-23 14:43 ` Stefan Monnier
2022-07-23 15:52 ` Eli Zaretskii
2022-07-23 16:31 ` Stefan Monnier
2022-07-23 17:07 ` Colorful line numbers Eli Zaretskii
2022-07-23 18:18 ` rmsbolt.el [Was: Colorful line numbers] João Távora
2022-07-23 18:11 ` João Távora
2022-07-23 14:53 ` Jay Kamat
2022-07-23 17:25 ` Stefan Monnier
2022-07-23 17:34 ` Eglot to core [Was: rmsbolt.el [Was: Colorful line numbers]] João Távora
2022-07-23 17:52 ` Stefan Monnier
2022-07-24 18:58 ` João Távora
2022-07-24 19:04 ` Stefan Monnier
2022-07-25 1:05 ` Po Lu
2022-07-25 2:45 ` Stefan Monnier
2022-07-25 5:55 ` Philip Kaludercic
2022-07-25 15:31 ` Stefan Monnier
2022-07-25 6:23 ` Po Lu
2022-07-25 10:49 ` Bozhidar Batsov
2022-07-25 11:01 ` João Távora
2022-07-25 11:50 ` Felician Nemeth
2022-07-25 12:27 ` João Távora
2022-07-25 12:29 ` João Távora
2022-07-25 15:00 ` Felician Nemeth
2022-07-25 15:41 ` João Távora
2022-07-26 8:12 ` Felician Nemeth
2022-07-26 8:21 ` João Távora
2022-07-26 8:55 ` Felician Nemeth
2022-07-25 16:07 ` Max Brieiev
2022-07-25 17:05 ` João Távora
2022-07-25 15:33 ` Stefan Monnier
2022-07-22 12:18 ` Colorful line numbers Dmitry Gutov
2022-07-22 12:38 ` Stefan Monnier
2022-07-22 13:41 ` Dmitry Gutov
2022-07-22 14:01 ` João Távora
2022-07-22 23:32 ` Stefan Monnier
2022-07-23 18:50 ` Dmitry Gutov
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=CALDnm50Ob0zQoxDN9bREGHwxYb6n_k7HEObq+FaXdiSGGoAQzg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jaygkamat@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).