unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: reader <gertopc@proton.me>
Cc: emacs-devel@gnu.org
Subject: Re: Dropping the dashes when displying command names
Date: Wed, 06 Dec 2023 14:21:30 +0200	[thread overview]
Message-ID: <83lea74j3p.fsf@gnu.org> (raw)
In-Reply-To: <_KCa7hG1yWNmsudi7IEVXqaPHv5UL6YTHaXRGo4P6JuRsO3QG20n0TbgJUmDRJVX6_22e0Jls3A_omOZTLNmIzNkHU2jJfs2D_me-zyv0c0=@proton.me> (message from reader on Tue, 05 Dec 2023 17:48:30 +0000)

> Date: Tue, 05 Dec 2023 17:48:30 +0000
> From: reader <gertopc@proton.me>
> 
> M-x presents you a list of interactive commands. They are lisp commands, but the user is concerned
> with their name when looking for a command, so displaying command names with spaces instead of
> dashes can make a more readable, cleaner presentation.
> 
> So instead of this:
> 
> delete-active-region 
> delete-char (<delete>) 
> delete-directory 
> delete-file-local-variable 
> delete-frame (C-x 5 0) 
> delete-matching-lines (flush-lines) 
> delete-other-frames (C-x 5 1) 
> delete-other-windows-vertically 
> delete-region 
> delete-trailing-whitespace 
> 
> it would look like this:
> 
> delete active region 
> delete char (<delete>) 
> delete directory 
> delete file local variable 
> delete frame (C- x 5 0) 
> delete matching lines (flush lines) 
> delete other frames (C-x 5 1) 
> delete other windows vertically 
> delete region 
> delete trailing whitespace 

IMO, this is only feasible if we also accept command invocation via
"M-x" with spaces instead of dashes (and even then as an opt-in
behavior).  The current behavior has the huge advantage of showing
what exactly you should type to invoke each command, whereas replacing
dashes with spaces loses that important feature.



  parent reply	other threads:[~2023-12-06 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 17:48 Dropping the dashes when displying command names reader
2023-12-06  3:50 ` Bob Rogers
2023-12-06  6:40   ` reader
2023-12-06 12:34     ` Eli Zaretskii
2023-12-06 15:28     ` [External] : " Drew Adams
2023-12-09  4:06       ` Richard Stallman
2023-12-06 12:21 ` Eli Zaretskii [this message]
2023-12-06 17:12   ` reader
2023-12-06 17:45     ` Eli Zaretskii

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=83lea74j3p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gertopc@proton.me \
    /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).