From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dean <laszlomail@protonmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Would you say this information window is well designed?
Date: Mon, 22 Feb 2021 20:48:38 +0200 [thread overview]
Message-ID: <83sg5oueex.fsf@gnu.org> (raw)
In-Reply-To: <YK1uEecrGm0aRoUVk27N1XPiCtBkkLto-CnUMp8uEfAAvqR33l0z7Va1bLJg6amys-ZQbJn3Z9uQ_gtRjlxRYHPDwj9RT0PoqSj72YPf1QI=@protonmail.com> (message from Peter Dean on Mon, 22 Feb 2021 18:37:20 +0000)
> Date: Mon, 22 Feb 2021 18:37:20 +0000
> From: Peter Dean <laszlomail@protonmail.com>
>
> I mean is it easy to parse? Is it appealing?
>
> https://i.imgur.com/KIWQE60.png
>
> It could use some spacing (e.g. a newline after the first line
> and Documentation), some colors (e.g. highlight symbols in
> ‘...’), and so on.
Patches are welcome for adding more colors to the *Help* buffers.
As to the newline, we are discussing that, as you are well aware.
> The package Helpful improves the default Help look. Some ideas
> for coloring and formatting could be borrowed from it to make the
> default mode more appealing, less spartan:
>
> https://raw.githubusercontent.com/Wilfred/helpful/master/screenshots/helpful.png
I won't object making something like that an optional feature, but
doing this by default is annoying, IMO: it's too much unsolicited
info. If, after reading the doc string, I want to look up the symbol
in the Info manual, I can do that with 2 keystrokes, I don't need
Emacs to show it to me unconditionally.
next prev parent reply other threads:[~2021-02-22 18:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 18:37 Would you say this information window is well designed? Peter Dean
2021-02-22 18:48 ` Eli Zaretskii [this message]
2021-02-22 19:23 ` Dmitry Gutov
2021-02-22 19:28 ` Eli Zaretskii
2021-02-22 20:28 ` Joost Kremers
2021-02-22 21:49 ` Dmitry Gutov
2021-02-22 21:57 ` Lars Ingebrigtsen
2021-02-22 22:30 ` [External] : " Drew Adams
2021-02-23 0:45 ` Stefan Kangas
2021-02-23 5:34 ` Drew Adams
2021-02-23 5:46 ` Drew Adams
2021-02-23 5:54 ` Peter Dean
2021-02-23 15:22 ` Eli Zaretskii
2021-02-23 15:29 ` Peter Dean
2021-02-23 16:00 ` Eli Zaretskii
2021-02-23 17:32 ` Peter Dean
2021-02-23 17:40 ` Eli Zaretskii
2021-02-23 17:59 ` Peter Dean
2021-02-23 18:26 ` Eli Zaretskii
2021-02-23 19:36 ` Peter Dean
2021-02-23 19:46 ` Eli Zaretskii
2021-02-23 21:58 ` Peter Dean
2021-02-24 3:25 ` Eli Zaretskii
2021-02-27 21:44 ` Dmitry Gutov
2021-02-28 17:32 ` Eli Zaretskii
2021-03-01 5:22 ` Richard Stallman
2021-02-23 5:44 ` Drew Adams
2021-02-23 14:18 ` Lars Ingebrigtsen
2021-02-23 15:44 ` Drew Adams
2021-02-23 16:15 ` Stefan Kangas
2021-02-23 16:28 ` Drew Adams
2021-02-22 21:19 ` Stefan Kangas
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=83sg5oueex.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=laszlomail@protonmail.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 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).