From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: jporterbugs@gmail.com, larsi@gnus.org,
yilkalargawworkneh@gmail.com, 56820@debbugs.gnu.org
Subject: bug#56820: outline-minor-mode replacing the first character with an arrow
Date: Thu, 08 Sep 2022 11:37:17 +0300 [thread overview]
Message-ID: <83fsh2feiq.fsf@gnu.org> (raw)
In-Reply-To: <86v8py5of4.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 08 Sep 2022 10:13:35 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org,
> yilkalargawworkneh@gmail.com, 56820@debbugs.gnu.org
> Date: Thu, 08 Sep 2022 10:13:35 +0300
>
> > Or maybe the fringe should be enhanced in some way where it can handle
> > multiple fringe icons in the same position. I'm not sure how that would
> > work though...
>
> I don't yet know the difference in implementation of fringes, margins and
> display-line-numbers, and whether they all use columns from the text area,
> and how easy would be to enhance their current implementation.
In the interests of being on the same page wrt terminology:
. "text area" doesn't include the margins
. the fringes are a separate area of the display, also outside of
the text area
. display-line-numbers _does_ show the line numbers in the text area
. a basic difference between the fringes and the margins is that
margins are basically special-purpose areas for displaying text,
whereas the fringes can only display images
. the most important difference between display in the margins and
display in the text area is that we don't support continuation in
the margins: if the text written there is longer than the margin
can display, the text is truncated, i.e. glyphs beyond what fits
will not be visible
next prev parent reply other threads:[~2022-09-08 8:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 10:39 bug#56820: outline-minor-mode replacing the first character with an arrow Yilkal Argaw
2022-07-29 11:03 ` Eli Zaretskii
2022-07-29 11:03 ` Tassilo Horn
2022-07-29 12:03 ` John Yates
2022-07-29 12:19 ` Tassilo Horn
2022-07-29 11:04 ` Eli Zaretskii
2022-07-29 11:21 ` bug#56820: " Lars Ingebrigtsen
2022-07-30 3:27 ` Yilkal Argaw
2022-07-30 4:40 ` Jim Porter
2022-07-30 9:24 ` Yilkal Argaw
2022-07-30 11:52 ` Lars Ingebrigtsen
2022-07-30 12:48 ` Yilkal Argaw
2022-07-30 12:54 ` Lars Ingebrigtsen
2022-07-30 13:00 ` Yilkal Argaw
2022-07-30 19:26 ` Jim Porter
2022-08-31 16:20 ` Juri Linkov
2022-09-04 17:02 ` Juri Linkov
2022-09-04 18:09 ` Eli Zaretskii
2022-09-04 18:54 ` Eli Zaretskii
2022-09-05 11:08 ` Lars Ingebrigtsen
2022-09-06 16:05 ` Juri Linkov
2022-09-06 16:28 ` Eli Zaretskii
2022-09-06 16:34 ` Juri Linkov
2022-09-06 16:45 ` Eli Zaretskii
2022-09-07 18:36 ` Juri Linkov
2022-09-07 18:50 ` Eli Zaretskii
2022-09-08 7:10 ` Juri Linkov
2022-09-08 8:32 ` Eli Zaretskii
2022-09-08 17:39 ` Juri Linkov
2022-09-08 17:45 ` Eli Zaretskii
2022-09-08 19:32 ` Juri Linkov
2022-09-07 20:01 ` Jim Porter
2022-09-08 7:13 ` Juri Linkov
2022-09-08 8:37 ` Eli Zaretskii [this message]
2022-09-08 12:01 ` Lars Ingebrigtsen
2022-09-08 13:39 ` Eli Zaretskii
2022-09-08 13:40 ` Lars Ingebrigtsen
2022-09-08 14:03 ` Eli Zaretskii
2022-09-09 17:04 ` Lars Ingebrigtsen
2022-09-09 18:01 ` Eli Zaretskii
2022-09-10 4:36 ` Lars Ingebrigtsen
2022-09-10 6:21 ` Eli Zaretskii
2022-09-08 11:45 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-07 12:46 ` Lars Ingebrigtsen
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=83fsh2feiq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56820@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=yilkalargawworkneh@gmail.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 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.