From: Juri Linkov <juri@linkov.net>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Jim Porter <jporterbugs@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
57082@debbugs.gnu.org
Subject: bug#57082: 29.0.50; emacs-news-view-mode breakage
Date: Wed, 10 Aug 2022 11:07:14 +0300 [thread overview]
Message-ID: <86fsi4cyhd.fsf@mail.linkov.net> (raw)
In-Reply-To: <87zggcwn0n.fsf@gmx.net> (Stephen Berman's message of "Wed, 10 Aug 2022 09:55:36 +0200")
>> 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.
>
> Ah, of course, I didn't even think to look there (oops again).
>
> diff --git a/lisp/outline.el b/lisp/outline.el
> index 7750f9a75d..8132043097 100644
> --- a/lisp/outline.el
> +++ b/lisp/outline.el
> @@ -294,16 +294,16 @@ outline-minor-mode-use-buttons
> :version "29.1")
>
> (define-icon outline-open button
> - '((emoji "▶️")
> - (symbol " ⯈ ")
> + '((emoji "🔽")
> + (symbol " ⯆ ")
> (text " open "))
> "Icon used for buttons for opening a section in outline buffers."
> :version "29.1"
> :help-echo "Open this section")
It seems the problem is somewhere else - in code that uses these definitions,
because here semantically everything is correct: the outline-open button
for opening a section means that the current state of the button is closed.
This assumes that in "outline-open" the word "open" is a verb.
next prev parent reply other threads:[~2022-08-10 8:07 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
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 [this message]
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=86fsi4cyhd.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=57082@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--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).