From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-devel@gnu.org, rms@gnu.org, raman@google.com
Subject: Re: Fwd: M-x shell question
Date: Fri, 19 Aug 2016 10:18:08 +0300 [thread overview]
Message-ID: <838tvtdy6n.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY3_vHC27QOcs3zAofxoBTnEWZi=VvB2n=60qPFbgRfTvw@mail.gmail.com> (message from Kaushal Modi on Fri, 19 Aug 2016 05:49:15 +0000)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Fri, 19 Aug 2016 05:49:15 +0000
> Cc: raman@google.com, emacs-devel@gnu.org
>
> On Fri, Aug 19, 2016 at 1:29 AM Richard Stallman <rms@gnu.org> wrote:
>
> That name is logical, but inconvenient: you have to type s h e SPC SPC c d.
>
> 'shell-this-directory' is almost as inconvenient: s h e SPC SPC t.
>
> I believe that keeping package name as first part of the command improves discoverability. If I were to look
> into what all commands are available related to 'shell', I can easily come across 'shell-cd' or 'shell-foo' with
> packages like ido or counsel or helm and start using it. But if the command is 'cd-shell', that reduces the
> discoverability (unless you have the fuzzy search enabled in packages like ido).
>
> I would just bind 'shell-cd' to a binding (like "C-c d s" maybe? :) ), if I find myself using it very often.
We could also have an alias for faster typing.
next prev parent reply other threads:[~2016-08-19 7:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 17:45 M-x shell question Richard Stallman
2016-08-17 18:09 ` raman
2016-08-17 19:04 ` Uwe Brauer
2016-08-17 21:13 ` raman
2016-08-18 14:07 ` Richard Stallman
2016-08-18 14:13 ` Fwd: " Kaushal Modi
2016-08-19 5:29 ` Richard Stallman
2016-08-19 5:49 ` Kaushal Modi
2016-08-19 7:18 ` Eli Zaretskii [this message]
2016-08-19 13:21 ` Robert Weiner
2016-08-19 14:14 ` Kaushal Modi
2016-08-19 14:35 ` Robert Weiner
2016-08-19 14:45 ` Kaushal Modi
2016-08-19 7:16 ` Eli Zaretskii
2016-08-18 14:22 ` Oleh Krehel
2016-08-18 15:11 ` Andreas Schwab
2016-08-19 2:53 ` Tino Calancha
2016-08-18 15:27 ` raman
2016-08-17 19:12 ` Robert Weiner
2016-08-17 20:24 ` Andreas Schwab
2016-08-18 3:51 ` Roland Winkler
2016-08-18 14:06 ` Richard Stallman
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=838tvtdy6n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=raman@google.com \
--cc=rms@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).