From: Gregory Heytings via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 42307@debbugs.gnu.org
Subject: bug#42307: Feature request: Visual block attribute for overlays
Date: Fri, 10 Jul 2020 18:57:16 +0000 [thread overview]
Message-ID: <alpine.NEB.2.21.2007101909320394.17046@sdf.lonestar.org> (raw)
In-Reply-To: <ae50e98e-d231-4aa9-98ad-b233dba63874@default>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
>
>> If you take the algorithm, it would start on the "u", extend to the
>> place it extends on the picture on the right, and on the next lines two
>> whitespace characters on the left would not be displayed as green
>> anymore (that is, the green area would start under the "f" of "(if".
>
> Why is that? That starting position of the second line's highlight
> doesn't correspond to anything "natural", does it? I would expect
> either that it starts as it does now, directly under the `(' of the
> first line, or directly under the `u' that started the overlay.
>
In fact it does, the overlay goes upwards above the comment below the "f"
of "(if". I attach a new picture between two arbitrary points that are
not brackets. I don't see any other way to define in simple terms how the
whitespace on the left should be trimmed. The "visualblock" would thus
highlight all the text of the block between overlay-begin and overlay-end,
and would be a rectangle except for the first and last lines, that is,
except before overlay-begin and after overlay-end.
>
> In any case, overlays, and highlighting, are not just for code.
>
Indeed. I think the proposed "visualblock" attribute is general and
simple enough that it could be used not only for code. E.g. it can be
used to highlight a portion of text with whitespace on the left, a TODO
item, say.
Gregory
[-- Attachment #2: Type: image/png, Size: 212444 bytes --]
next prev parent reply other threads:[~2020-07-10 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 8:24 bug#42307: Feature request: Visual block attribute for overlays Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-10 14:56 ` Drew Adams
2020-07-10 15:24 ` Drew Adams
2020-07-10 16:02 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-10 16:42 ` Drew Adams
2020-07-10 18:57 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-07-10 21:26 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-11 23:50 ` Juri Linkov
2020-07-12 1:25 ` Drew Adams
2020-07-12 8:21 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-12 23:59 ` Juri Linkov
2020-07-13 6:45 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
-- strict thread matches above, loose matches on Subject: below --
2020-07-08 17:19 bug#42347: " Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-14 2:32 ` Eli Zaretskii
2020-07-14 7:38 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-14 14:55 ` Eli Zaretskii
2020-07-14 15:45 ` bug#42307: " Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-14 16:34 ` Eli Zaretskii
2020-07-14 17:01 ` bug#42307: " Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-14 17:10 ` Eli Zaretskii
2020-07-14 17:20 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-14 4:23 ` bug#42347: " Drew Adams
2020-07-14 7:49 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-14 14:48 ` Drew Adams
2020-07-14 15:53 ` bug#42307: " Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=alpine.NEB.2.21.2007101909320394.17046@sdf.lonestar.org \
--to=bug-gnu-emacs@gnu.org \
--cc=42307@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=ghe@sdf.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.