From: Eli Zaretskii <eliz@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: 16992@debbugs.gnu.org
Subject: bug#16992: feature request: background images
Date: Fri, 08 Nov 2024 20:50:35 +0200 [thread overview]
Message-ID: <86ldxto8zo.fsf@gnu.org> (raw)
In-Reply-To: <ea66e075-2cb0-416e-9fd3-e04fb24ffec7@imayhem.com> (message from Cecilio Pardo on Fri, 8 Nov 2024 17:42:48 +0100)
> Date: Fri, 8 Nov 2024 17:42:48 +0100
> From: Cecilio Pardo <cpardo@imayhem.com>
>
> On 08/11/2024 16:46, Eli Zaretskii wrote:
>
> > So showing a vertical line for the fill-column indication would need
> > to define a background image for a frame? How do we control the
> > horizontal coordinate where the line is drawn?
>
> No, the background image (if present) is drawn first, then 'dynamic'
> things like the indicator are drawn over, with the corresponding drawing
> api. We are doing both things. In the patch, the fill-column indicator
> line is drawn by looking directly at the value of fill_column. But I
> think it would be better to allow lisp to define multiple vertical
> lines, with the desired position.
So what is the Lisp API for drawing those "dynamic" things? AFAIU,
you've only shown the API to set a single static background image.
> > Btw, what happens when text is scrolled horizontally?
>
> Nothing special. Besides redrawing everything.
Is the background image scrolled or isn't it?
> > Is this only going to work with fixed images? Then I guess features
> > like showing vertical lines as indentation indicators, like those
> > here:
> >
> > https://techpress.net/how-to-show-hide-indent-dots-in-vscode/
> >
> > will not be possible?
>
> Yes. Those are not part of the image. We use the same mechanism to draw
> on the background, but they are independent. We can use them without
> background images at all.
>
> Some of these things are easy to do, like the fill indicator, which
> doesn't depend on the contents of the buffer. Indentation lines are much
> more complex.
Those "dynamic" drawings are the most wanted feature that is currently
missing. And the challenge is to implement them in a way that won't
make redisplay significantly slower, e.g. due to disabled
optimizations (like scrolling_window).
next prev parent reply other threads:[~2024-11-08 18:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 23:19 bug#16992: Feature request David Englund
2014-03-12 6:26 ` Glenn Morris
2020-08-04 9:50 ` Lars Ingebrigtsen
2021-11-05 13:42 ` bug#20647: bug#16992: feature request: background images Stefan Kangas
[not found] ` <CALaEO5W3+aEtwPr7bt3zNbkNw386GXpE-vkoRoojS0HqOvDQkQ@mail.gmail.com>
2021-11-15 7:08 ` Stefan Kangas
2021-11-16 11:10 ` tadashi watanabe
2024-11-06 22:34 ` Cecilio Pardo
2024-11-07 1:43 ` Stefan Kangas
2024-11-07 6:46 ` Cecilio Pardo
2024-11-07 6:04 ` Eli Zaretskii
2024-11-08 13:59 ` Cecilio Pardo
2024-11-08 15:46 ` Eli Zaretskii
2024-11-08 16:42 ` Cecilio Pardo
2024-11-08 18:50 ` Eli Zaretskii [this message]
2024-11-08 19:20 ` Cecilio Pardo
2024-11-09 7:44 ` 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=86ldxto8zo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16992@debbugs.gnu.org \
--cc=cpardo@imayhem.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).