all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: jporterbugs@gmail.com, yilkalargawworkneh@gmail.com,
	56820@debbugs.gnu.org, juri@linkov.net
Subject: bug#56820: outline-minor-mode replacing the first character with an arrow
Date: Fri, 09 Sep 2022 21:01:56 +0300	[thread overview]
Message-ID: <83sfl0bf57.fsf@gnu.org> (raw)
In-Reply-To: <87y1usv5rz.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  09 Sep 2022 19:04:00 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: jporterbugs@gmail.com,  juri@linkov.net,  yilkalargawworkneh@gmail.com,
>   56820@debbugs.gnu.org
> Date: Fri, 09 Sep 2022 19:04:00 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Hm.  Could we do away with the fringes and just use the margins, long
> >> term?
> >
> > Depends for what purposes.  The fringes generally take less space for
> > small enough images, and "other editors" provide similar features,
> > including for breakpoint markers.
> 
> I meant whether we could get rid of the current fringe implementation
> (which doesn't allow displaying normal images) and just use the margin
> code for the fringes instead.

We could, but why would we want to?  If we want to display other types
of (small) images on the fringes, it should be almost straightforward
to implement.  The actual code that draws the bitmaps on the fringes
is specific to the terminal, and we have separate implementations for
X, w32, Cairo, etc.  It shouldn't be too hard to support other images
there.





  reply	other threads:[~2022-09-09 18:01 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
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 [this message]
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=83sfl0bf57.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.