unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Ideas to improve the output of C-h m?
Date: Fri, 1 May 2020 12:16:20 -0400	[thread overview]
Message-ID: <01f4b0be-c4c6-beff-593f-74508f321552@gmail.com> (raw)
In-Reply-To: <jwvh7wzwtg3.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

On 01/05/2020 11.55, Stefan Monnier wrote:
>> I have pasted at the botom of this email the output of the current C-h
>> m and the output of the code I wrote a while ago.  Here's how it looks
>> for a single entry, to see the difference (note that unlike C-h m, it
>> currently groups keybindings that map to the same command):
> 
> I think grouping is a good idea, tho the current "columnar" output has
> its advantages as well.
> 
>>     ‘C-c @’ (outline-mark-subtree)
>>       Mark the current subtree in an outlined document.
>>     ‘C-c C-n’ (outline-next-visible-heading)
>>       Move to the next visible heading line.
> 
> More importantly, while I like the idea of showing the first line of the
> docstring, I find the above much harder to read.  It makes the common
> `C-c` and `outline-` prefixes much less obvious so you can't so easily
> focus on the other parts to find what you're looking for.

That's fair, though with a bit of luck that was partly due to the text-only output.  WDYT of the attached screenshot? (of course the issue remains to some extent, but hopefully the font size, face, and spacing changes help?)
(I also removed the parentheses and the quotes, and re-added the vertical alignment)

[-- Attachment #2: light-theme.png --]
[-- Type: image/png, Size: 129812 bytes --]

[-- Attachment #3: dark-theme.png --]
[-- Type: image/png, Size: 141328 bytes --]

  reply	other threads:[~2020-05-01 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 14:34 Ideas to improve the output of C-h m? Clément Pit-Claudel
2020-05-01 15:55 ` Stefan Monnier
2020-05-01 16:16   ` Clément Pit-Claudel [this message]
2020-05-01 17:44     ` Stefan Monnier
2020-05-01 23:02     ` Stefan Kangas
2020-05-02  3:24       ` Clément Pit-Claudel
2020-05-06 13:34         ` Stefan Kangas
     [not found]         ` <jwv5zd9wyj6.fsf-monnier+emacs@gnu.org>
     [not found]           ` <CADwFkmmhezor_jCwff8YH2wVvnyb7Rf=7YnLeeN_aRehkw8beA@mail.gmail.com>
2020-08-21  0:27             ` scratch/substitute-command-keys: C conversion of s-c-k Stefan Kangas
2020-05-03  3:39       ` Ideas to improve the output of C-h m? Richard Stallman
2020-05-02  4:05 ` Jean-Christophe Helary

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=01f4b0be-c4c6-beff-593f-74508f321552@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=emacs-devel@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).