unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bigger fringe bitmaps
Date: Thu, 17 Mar 2022 09:34:08 +0100	[thread overview]
Message-ID: <87sfrhklob.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <83mthpgfao.fsf@gnu.org>

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 like the idea of using 🢱 (or ⤶⤷) for wrapped text, 🮗 as a
>> end-of-buffer, and so on. Easily scaled, and nicely antialiased.
>
> You disregard the issue of which fonts support what characters in the
> relevant Unicode blocks.

Definitely.

> 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.

>> 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.

> 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.

(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?)



  reply	other threads:[~2022-03-17  8:34 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 [this message]
2022-03-17  9:30         ` Eli Zaretskii
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=87sfrhklob.fsf@wavexx.thregr.org \
    --to=wavexx@thregr.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).