From: Eli Zaretskii <eliz@gnu.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bigger fringe bitmaps
Date: Thu, 17 Mar 2022 11:30:25 +0200 [thread overview]
Message-ID: <83lex9gc3y.fsf@gnu.org> (raw)
In-Reply-To: <87sfrhklob.fsf@wavexx.thregr.org> (message from Yuri D'Elia on Thu, 17 Mar 2022 09:34:08 +0100)
> From: Yuri D'Elia <wavexx@thregr.org>
> Cc: emacs-devel@gnu.org
> Date: Thu, 17 Mar 2022 09:34:08 +0100
>
> On Thu, Mar 17 2022, Eli Zaretskii wrote:
> > I did comment on that. To repeat: it could be a useful new feature,
> > but I don't think it should be _the_ solution for showing stuff on the
> > fringes on hidpi terminals; we should be able to produce legible
> > display of the bitmaps on those terminals.
>
> Seen it, I was just prompting for more feedback on the idea and discuss
> if this could be a good and/or bad idea.
I think it's a good idea. It "just" needs to be implemented...
> > Solving this in the limited fringe screen estate will need some
> > non-trivial ideas. And what about 'half-width' or 'minimal'
> > fringe-styles?
>
> I mentally imagine this as just scaling the font smaller to fit the
> fringe width, centering each character vertically.
Emacs doesn't know how to scale a font at display time. The font is
"scaled" (or, rather, selected) when the face using the font is
defined. So dynamically changing the font of a face when the user
plays with fringe-style would be another complication that needs to be
taken care of.
> >> Especially the fact that this would potentially mean an usable fringe
> >> mode on character displays that can be toggled, so that you don't need
> >> to provide an alternate signaling mechanism if you rely on the fringe to
> >> show makers (like gud).
> >
> > I don't think I follow. Emacs doesn't support fringes on TTY
> > displays, so what do you mean by "usable fringe mode on character
> > displays"?
>
> That would be part of the advantage of allowing a character to be used
> in lieu of a bitmap (either as a feature or as a fallback).
>
> On a TTY we could just reserve the first/last column for the "fringe"
> and display the lowest-common-denominator format available.
How is this different from what overlay-arrow already does? It is
even more flexible, as it is not limited to a single column.
> > This is already supported, see overlay-arrow-string. Or do you mean
> > something else?
>
> Yes, but it doesn't behave exactly in the same way as the fringe does.
In what way does it not behave the same?
> (and I also as I just discovered, if I disable the fringe on a graphical
> display I do not get the overlay arrows as a fallback -- or did I miss
> some variable to control this behavior?)
What did you try? See the "Overlay Arrow" node in the ELisp manual
for what is available.
next prev parent reply other threads:[~2022-03-17 9:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 17:57 Bigger fringe bitmaps Yuri D'Elia
2022-03-16 18:23 ` Eli Zaretskii
2022-03-17 0:31 ` Po Lu
2022-03-17 7:43 ` Yuri D'Elia
2022-03-17 8:21 ` Eli Zaretskii
2022-03-17 8:34 ` Yuri D'Elia
2022-03-17 9:30 ` Eli Zaretskii [this message]
2022-03-17 9:44 ` Yuri D'Elia
2022-03-17 12:57 ` Eli Zaretskii
2022-03-17 21:21 ` Yuri D'Elia
2022-03-18 6:22 ` Eli Zaretskii
2022-03-18 9:29 ` Yuri D'Elia
2022-03-18 14:52 ` [External] : " Drew Adams
2022-03-18 15:31 ` tomas
2022-03-18 16:08 ` Drew Adams
2022-03-18 17:19 ` tomas
2022-03-18 23:14 ` Po Lu
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=83lex9gc3y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wavexx@thregr.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).