unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: A different way to interactively pass options to commands
Date: Wed, 17 Feb 2021 23:24:29 +0100	[thread overview]
Message-ID: <87o8giz61u.fsf@gnus.org> (raw)
In-Reply-To: <87ft1u9xhh.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Wed, 17 Feb 2021 22:48:42 +0100")

Óscar Fuentes <ofv@wanadoo.es> writes:

> For instance: showing the log of the current
> repository with default options is `ll' (two els); showing the log of
> all branches is `la'; showing the log of all branches along with the
> corresponding patch for each commit is `l-pa', and so on.

I see; interesting.

> So, could Emacs take advantage of something like this? I think so.

Yes, it does sound quite attractive.  For instance, in Gnus, when
responding to a message, there's...  I don't know how many commands.
Let's see:

S F		gnus-summary-followup-with-original
S L		gnus-summary-reply-to-list-with-original
S N		gnus-summary-followup-to-mail-with-original
S R		gnus-summary-reply-with-original
S V		gnus-summary-very-wide-reply-with-original
S W		gnus-summary-wide-reply-with-original
S f		gnus-summary-followup
S n		gnus-summary-followup-to-mail
S r		gnus-summary-reply
S v		gnus-summary-very-wide-reply
S w		gnus-summary-wide-reply
S B R		gnus-summary-reply-broken-reply-to-with-original
S B r		gnus-summary-reply-broken-reply-to

13!  Geez.  Anyway, the interface you describe would fit this use case
well, it seems to me: The choices are whether to include the original or
not, and what subset of the To/Cc's to include in the set...  Currently,
users are probably tapping `S C-h' and then learn what the binding is,
and then using that.  And then forgetting until the next time.

A Magit-like popup menu would probably be a much superior interface
here, I think?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  parent reply	other threads:[~2021-02-17 22:24 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17 19:50 A different way to interactively pass options to commands Clemens
2021-02-17 20:07 ` Stefan Monnier
2021-02-17 20:20   ` Lars Ingebrigtsen
2021-02-17 22:05     ` Stefan Monnier
2021-02-19  5:41   ` Richard Stallman
2021-02-19 14:30     ` Stefan Monnier
2021-02-17 20:09 ` Lars Ingebrigtsen
2021-02-17 20:32   ` Clemens
2021-02-17 20:42     ` Lars Ingebrigtsen
2021-02-17 20:58       ` Clemens
2021-02-17 21:24       ` Clemens
2021-02-17 22:15         ` Stefan Monnier
2021-02-17 21:48   ` Óscar Fuentes
2021-02-17 22:23     ` Stefan Monnier
2021-02-17 22:47       ` Óscar Fuentes
2021-02-17 23:52         ` Clemens
2021-02-17 22:24     ` Lars Ingebrigtsen [this message]
2021-02-17 23:18       ` Óscar Fuentes
2021-02-18 10:09         ` Lars Ingebrigtsen
2021-02-18  1:16       ` Doug Davis
2021-02-18 10:03         ` Lars Ingebrigtsen
2021-02-18 10:39           ` Kévin Le Gouguec
2021-02-18 10:52             ` Lars Ingebrigtsen
2021-02-18 12:13               ` Dmitry Gutov
2021-02-18 17:45                 ` Stefan Kangas
2021-02-18 17:55                   ` Dmitry Gutov
2021-02-18 18:32                     ` Stefan Kangas
2021-02-19 11:59                       ` Lars Ingebrigtsen
2021-02-18 16:11               ` Óscar Fuentes
2021-02-18 15:40             ` Stefan Monnier
2021-02-18 16:28               ` Development snapshots on GNU ELPA (was: A different way to interactively pass options to commands) Kévin Le Gouguec
2021-02-19 12:01               ` A different way to interactively pass options to commands Lars Ingebrigtsen
2021-02-19 14:32                 ` Stefan Monnier
2021-02-21 14:55                   ` GNU-devel and NonGNU-devel (was: A different way to interactively pass options to commands) Basil L. Contovounesios
2021-02-21 20:25                     ` GNU-devel and NonGNU-devel Stefan Monnier
2021-02-25  2:19                       ` Basil L. Contovounesios
2021-02-19 15:44               ` A different way to interactively pass options to commands Jonas Bernoulli
2021-02-19 18:23                 ` Clemens
2021-02-22  0:18                   ` Jonas Bernoulli
2021-02-22  2:39                     ` T.V Raman
2021-02-22  9:17                     ` Questions about transient (was: Re: A different way to interactively pass options to commands) Joost Kremers
2021-02-22 15:08                       ` Jonas Bernoulli
2021-02-22 21:06                         ` Joost Kremers
2021-02-22 16:25                       ` [External] : " Drew Adams
2021-02-23 12:15                     ` A different way to interactively pass options to commands Stephen Leake
2021-02-23 19:06                       ` Jonas Bernoulli
2021-02-19  5:42     ` Richard Stallman
2021-02-19  6:32       ` Stefan Kangas
2021-02-21 10:28   ` Phil Sainty

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=87o8giz61u.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).