From: Aleksandr Petrosyan <a-p-petrosyan@yandex.ru>
To: 46926@debbugs.gnu.org
Subject: bug#46926: Remove quotes from the highlighted symbols list
Date: Mon, 15 Mar 2021 00:36:00 +0400 [thread overview]
Message-ID: <FE945BD6-9BBB-4C57-890A-9D45081F8E40@yandex.ru> (raw)
In-Reply-To: <T1Tq9JA9J_-FcH3lAIDQ5ypP1a1fvrCRCpazRSLNVdibdSfdfHKWMAWaFXtQ943Vv67pN6gFsm9g3tP7T1TgZmxXBID1YSfBAUQUBCTTpss=@protonmail.com>
Dear all,
UI designer from KDE/Qt/Maui.
I agree that there are orthogonal design decisions at play here: quotes indicate that the object is a symbol. Then the link face indicates that it is also something that can be expanded upon. However, the quotes, while useful for “someone in the know”, are distracting in text.
My preferred solution, would be to use a code face, specifically for symbols and highlight the symbol such that it appears as every other symbol does in emacs lisp. One can inherit the monospace font from GTK to distinguish from documentation text. The link... it can be anything: it could be the documentation for the symbol, or the file which it’s defined in. A user needs to know *exactly* what’s going to happen if they click, so if it’s going to visit e.g. Python.el, and not the documentation of what Python.el is part of, it’s better to say explicitly “visit elisp file”. A button can serve better, but emacs has... ugly buttons and doesn’t use them very consistently, so a link is fine.
Sincerely
Aleksandr Petrosyan
prev parent reply other threads:[~2021-03-14 20:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 16:57 bug#46926: Remove the quotes from highlighted/linked symbols when displaying docs scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-04 17:19 ` Eli Zaretskii
2021-03-04 17:50 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-04 18:36 ` Eli Zaretskii
2021-03-04 19:08 ` bug#46926: [External] : " Drew Adams
2021-03-04 20:23 ` Lars Ingebrigtsen
2021-03-04 21:40 ` bug#46926: [External] : " Drew Adams
2021-03-12 1:38 ` Stefan Kangas
2021-03-13 5:50 ` Richard Stallman
2021-03-13 6:08 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 7:02 ` Stefan Kangas
2021-03-13 7:44 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 7:43 ` Eli Zaretskii
2021-03-13 7:51 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 8:39 ` Eli Zaretskii
2021-03-13 16:24 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 16:36 ` Eli Zaretskii
2021-03-13 17:05 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 17:08 ` Eli Zaretskii
2021-03-15 17:28 ` Dmitry Gutov
2021-03-15 17:51 ` Eli Zaretskii
2021-03-15 23:20 ` Dmitry Gutov
2021-03-16 2:37 ` Stefan Kangas
2021-03-16 3:36 ` Eli Zaretskii
2021-03-16 3:51 ` Stefan Kangas
2021-03-16 12:36 ` Eli Zaretskii
2021-03-16 13:01 ` Gregory Heytings
2021-03-16 13:28 ` Eli Zaretskii
2021-03-16 16:27 ` Gregory Heytings
2021-03-16 23:12 ` Lars Ingebrigtsen
2021-03-17 6:00 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-17 13:09 ` Eli Zaretskii
2021-03-17 15:53 ` bug#46926: [External] : " Drew Adams
2021-03-16 15:41 ` Dmitry Gutov
2021-03-16 18:44 ` Eli Zaretskii
2021-03-16 3:32 ` Eli Zaretskii
2021-03-16 15:45 ` Dmitry Gutov
2021-03-16 15:49 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 0:25 ` Lars Ingebrigtsen
2021-03-13 17:06 ` Stefan Kangas
2021-03-13 18:27 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 6:02 ` Richard Stallman
2021-03-04 20:31 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-04 17:58 ` bug#46926: [External] : " Drew Adams
2021-03-04 18:40 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-04 19:26 ` Drew Adams
2021-03-04 20:36 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-06 5:11 ` Richard Stallman
2021-03-14 20:36 ` Aleksandr Petrosyan [this message]
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=FE945BD6-9BBB-4C57-890A-9D45081F8E40@yandex.ru \
--to=a-p-petrosyan@yandex.ru \
--cc=46926@debbugs.gnu.org \
/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).