From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: larsi@gnus.org, yilkalargawworkneh@gmail.com, 56820@debbugs.gnu.org
Subject: bug#56820: outline-minor-mode replacing the first character with an arrow
Date: Tue, 06 Sep 2022 19:28:04 +0300 [thread overview]
Message-ID: <83tu5kii23.fsf@gnu.org> (raw)
In-Reply-To: <86edwotx6n.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 06 Sep 2022 19:05:52 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: yilkalargawworkneh@gmail.com, larsi@gnus.org, 56820@debbugs.gnu.org
> Date: Tue, 06 Sep 2022 19:05:52 +0300
>
> > . do we really need to hide the first character of the line by the
> > overlay? doesn't before-string work?
>
> Does using before-string allows moving the cursor into the button
> displayed with before-string?
I don't understand this question: currently the cursor cannot be moved
into the overlay anyway. And if the first character of the buffer's
line is not hidden below an overlay, why would we need to move cursor
into the overlay to begin with?
> > . wouldn't it be better if the arrow buttons were displayed in the
> > window's margin, and would thus avoid indenting the characters on
> > that line wrt the rest of the code?
>
> Same problem: the cursor can't be moved into the fringe indicator
> to be able to type RET on it.
I asked about the margins, not the fringe.
If you ask about RET, that is relevant for text-mode frames, where
buttons won't be used anyway, right? On GUI frames, people are
expected to click on the buttons, right?
> > . the buttons have a dark gray background that doesn't look good.
>
> The buttons that I see by default are much worse - their background is
> glaring orange.
So we need to make them more visually appealing.
next prev parent reply other threads:[~2022-09-06 16:28 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 [this message]
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
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=83tu5kii23.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56820@debbugs.gnu.org \
--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.