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 22:21:14 +0100 [thread overview]
Message-ID: <87fsngl0ue.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <83k0cshh43.fsf@gnu.org>
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).
I tried to copy/paste some buffers to see how it would "play". As a
first impression, it's a tradeoff I'd take over the overlay-arrow while
debugging for sure.
All modes.. mmh. It looks "different". But if I try to keep only the
right-side fringe, I undoubtedly like it and wouldn't mind the loss of
the column at all times.
I definitely need to try to mock an X11 screenshot to see how _that_
would look as well.
> You mean, when left fringe is enabled, right?
>
> I made the text there more accurate, thanks.
Yes. Thanks, very appreciated!
next prev parent reply other threads:[~2022-03-17 21:21 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsngl0ue.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 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.