From: Eli Zaretskii <eliz@gnu.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bigger fringe bitmaps
Date: Fri, 18 Mar 2022 08:22:13 +0200 [thread overview]
Message-ID: <83ee2zhjai.fsf@gnu.org> (raw)
In-Reply-To: <87fsngl0ue.fsf@wavexx.thregr.org> (message from Yuri D'Elia on Thu, 17 Mar 2022 22:21:14 +0100)
> From: Yuri D'Elia <wavexx@thregr.org>
> Cc: emacs-devel@gnu.org
> Date: Thu, 17 Mar 2022 22:21:14 +0100
>
> On Thu, Mar 17 2022, Eli Zaretskii wrote:
> >> I agree it's more powerful, but the overlay-arrow shares the same space
> >> with the buffer, so it can hide existing information. I like the fact
> >> that the fringe is a minimal, non-shared, space.
> >
> > How would you go about not sharing the screen space with the buffer,
> > when the display is a TTY? What else is there that we could use
> > instead?
>
> First/last column reserved when the "tty fringe" is on. On one hand,
> potentially more wasteful than the overlay-arrow. On the other, it would
> be guaranteed to be a single-character only (and any character there
> wouldn't overlap - making it clearly distinct).
How many hours will pass before someone requests a capability to use
more than just a single column? We already use two with "=>", so
going down to one with something like ">" will probably be considered
a regression by some.
So I think the current situation is better on balance.
next prev parent reply other threads:[~2022-03-18 6:22 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
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 [this message]
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=83ee2zhjai.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).