From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Generic dispatcher
Date: Mon, 01 Jul 2013 09:01:43 -0400 [thread overview]
Message-ID: <877ghajux4.fsf@lifelogs.com> (raw)
In-Reply-To: jwv4ncf2pek.fsf-monnier+emacs@gnu.org
On Sun, 30 Jun 2013 18:46:36 -0400 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
SM> For epa/eww/mhe/... I think we should introduce a generic dispatcher.
SM> The way I see it, it would look like:
SM> - M-x mail RET runs one of the mail backends. First time around it
SM> prompts the user to choose a MUA, then stores the result in a Custom
SM> var and doesn't prompt any more. This would rely on
SM> a mail-alternatives variable holding various MUAs such as Gnus, MH-E,
SM> ... and third party packages can easily register themselves in this
SM> list via their autoloads. The user can reconsider his choice with C-u
SM> M-x mail RET in which case she gets prompted again.
SM> - same for M-x irc RET
SM> - same for M-x encrypt RET
SM> - same for M-x browse RET
SM> - we could push this further (e.g. auctex vs tex-mode.el) but I'm not
SM> sure it'd be such a great idea.
I think that's a good idea. But (as I mentioned in the "Rename `eww' to
`web'" discussion) I think focusing on command names is the wrong
approach for usability. These should be first-class commands in every
way, accessible from a top-level menu and from a convenient key
sequence. Maybe new modeline icons that respond to clicks. I just feel
that putting them under `M-x whatever' will not help usability.
Ted
next prev parent reply other threads:[~2013-07-01 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 22:46 Generic dispatcher Stefan Monnier
2013-06-30 23:11 ` Xue Fuqiao
2013-06-30 23:42 ` Drew Adams
2013-07-01 7:43 ` Teemu Likonen
2013-07-01 13:01 ` Ted Zlatanov [this message]
2013-07-01 23:23 ` Stefan Monnier
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=877ghajux4.fsf@lifelogs.com \
--to=tzz@lifelogs.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).