From: Jim Porter <jporterbugs@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>, Juri Linkov <juri@linkov.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 57082@debbugs.gnu.org
Subject: bug#57082: 29.0.50; emacs-news-view-mode breakage
Date: Tue, 9 Aug 2022 17:03:25 -0700 [thread overview]
Message-ID: <db1ecebd-1113-6c7c-8eff-d22d6b1d8de1@gmail.com> (raw)
In-Reply-To: <87v8r1xj9u.fsf@gmx.net>
On 8/9/2022 1:18 PM, Stephen Berman wrote:
> On Tue, 09 Aug 2022 22:18:21 +0300 Juri Linkov <juri@linkov.net> wrote:
>
>> I noticed more problems: arrow directions are inverted - when an outline
>> is hidden the arrow direction is open; when it's shown then the button has
>> the closed state.
>
> The arrows behave the same as in *Help* with describe-bindings:
> outline-close (downward-pointing) when the body is hidden, outline-open
> (leftward-pointing) when the body is shown. Is that wrong?
I think that's wrong, yes. Every GUI I'm familiar with does it the other
way:
> Closed Item
v Open Item
> Closed Sub Item
This is the visual style used in GNOME (at least, the theme I'm using),
MS Windows, macOS, Firefox/Thunderbird, and probably others. More
importantly, it's also the style Emacs already uses elsewhere: see the
Customize UI.
The only other style I've seen is "-" for open items and "+" for closed
(because clicking "+" will *add* the children to the UI and "-" will
*remove* them). Emacs does that in the speedbar, for example.
>> It would be nicer if the color of the button depended on the outline's color,
>> e.g. blue for the top-level blue outline face, etc.
>
> I guess that would require using suitable images rather than emojis.
Images would be nice; Emacs already has some for the Customize UI that
could be reused.
For the NEWS file though (and especially programming modes). I still
think it'd be great to put the buttons in the fringe. That way the
buttons would never disrupt the contents of the file, e.g. by changing
how the indentation looks.
However, describe-bindings probably wants the buttons in the body, so
this would be yet another option, which adds complexity/maintenance
burden...
next prev parent reply other threads:[~2022-08-10 0:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 16:18 bug#57082: 29.0.50; emacs-news-view-mode breakage Stephen Berman
2022-08-09 18:23 ` Lars Ingebrigtsen
2022-08-09 19:18 ` Juri Linkov
2022-08-09 20:18 ` Stephen Berman
2022-08-10 0:03 ` Jim Porter [this message]
2022-08-10 7:39 ` Juri Linkov
2022-08-10 8:08 ` Gregory Heytings
2022-08-10 8:10 ` Juri Linkov
2022-08-10 8:24 ` Gregory Heytings
2022-08-10 15:17 ` Drew Adams
2022-08-10 7:55 ` Stephen Berman
2022-08-10 8:07 ` Juri Linkov
2022-08-12 12:50 ` Lars Ingebrigtsen
2022-08-12 12:49 ` Lars Ingebrigtsen
2022-08-12 12:51 ` Lars Ingebrigtsen
2022-08-10 7:36 ` Juri Linkov
2022-08-10 8:19 ` Stephen Berman
2022-08-10 18:45 ` Juri Linkov
2022-08-10 18:58 ` Stephen Berman
2022-08-11 6:44 ` Juri Linkov
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=db1ecebd-1113-6c7c-8eff-d22d6b1d8de1@gmail.com \
--to=jporterbugs@gmail.com \
--cc=57082@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=stephen.berman@gmx.net \
/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).