From: philip@warpmail.net (Philip K.)
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: simenheg@runbox.com, contovob@tcd.ie, emacs-devel@gnu.org,
juri@linkov.net
Subject: Re: New feature in project.el: Remembering the previously used projects
Date: Fri, 05 Jun 2020 13:59:36 +0200 [thread overview]
Message-ID: <87a71hvi3b.fsf@bulbul> (raw)
In-Reply-To: <b5f2cb35-3589-9cdf-ac9b-9e091718ab7b@yandex.ru> (message from Dmitry Gutov on Fri, 5 Jun 2020 14:44:38 +0300)
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 05.06.2020 11:33, Philip K. wrote:
>> Juri Linkov <juri@linkov.net> writes:
>>
>>> Is it possible to use key sequences, e.g. ‘s h’ for ‘shell’, ‘s e’ for ‘search’?
>>
>> Don't most people tend to use either shell, eshell or some other
>> terminal application? If I were to use shell, over eshell, I guess that
>> this would be somewhat annoying, at least by default.
>
> So what are you saying? Which option would you prefer?
I was questioning how many people switch between eshell and shell, so
that both would have to be part of the menu. One way out would be to
have a user option for "prefered shell", either in Emacs or as part of
project.el.
> Simply by the statement above, I'd probably choose to have only one of
> the commands in the default set, expecting the user to customize it, if
> they routinely use the other. And Eshell seems to be a tiny bit more
> popular (though I could be wrong here).
>
>> I was thinking that a "x" key could be added, which would invoke
>> execute-extended-command, but in the project root.
>
> Why not. Would you like to send a patch?
Sure, I'll try it out.
--
Philip K.
next prev parent reply other threads:[~2020-06-05 11:59 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 20:06 New feature in project.el: Remembering the previously used projects Dmitry Gutov
2020-05-28 23:05 ` Basil L. Contovounesios
2020-05-28 23:29 ` Dmitry Gutov
2020-05-29 7:31 ` Philip K.
2020-05-29 13:51 ` Dmitry Gutov
2020-05-29 15:54 ` Simen Heggestøyl
[not found] ` <871rn2ivne.fsf@simenheg@gmail.com>
2020-05-30 10:29 ` Philip K.
2020-06-02 17:04 ` Simen Heggestøyl
[not found] ` <5ed68784.1c69fb81.61518.35eeSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-03 11:28 ` Basil L. Contovounesios
2020-05-30 12:38 ` Dmitry Gutov
2020-06-02 17:14 ` Simen Heggestøyl
2020-05-30 21:57 ` Juri Linkov
2020-05-30 23:39 ` Dmitry Gutov
2020-06-01 23:01 ` Juri Linkov
2020-06-02 21:34 ` Dmitry Gutov
2020-06-03 20:13 ` Dmitry Gutov
2020-06-03 22:40 ` Juri Linkov
2020-06-03 23:13 ` Dmitry Gutov
2020-06-04 21:55 ` Juri Linkov
2020-06-04 22:37 ` Dmitry Gutov
2020-06-05 8:33 ` Philip K.
2020-06-05 8:42 ` Simen Heggestøyl
2020-06-05 11:44 ` Dmitry Gutov
2020-06-05 11:59 ` Philip K. [this message]
2020-06-05 13:59 ` Philip K.
2020-06-05 17:20 ` Dmitry Gutov
2020-06-06 1:24 ` Jamie Beardslee
2020-12-19 22:18 ` Dmitry Gutov
2020-06-06 23:46 ` Juri Linkov
2020-06-07 0:40 ` Dmitry Gutov
2020-06-07 22:38 ` Juri Linkov
2020-06-02 17:43 ` Simen Heggestøyl
[not found] ` <87a71l2wjf.fsf@simenheg@gmail.com>
2020-06-02 17:57 ` Dmitry Gutov
2020-06-03 22:34 ` Juri Linkov
2020-06-03 23:17 ` Dmitry Gutov
2020-06-04 18:33 ` Simen Heggestøyl
2020-06-04 21:58 ` Juri Linkov
[not found] ` <5ed68fe1.1c69fb81.45e50.0c7cSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-03 11:28 ` Basil L. Contovounesios
2020-05-31 13:00 ` Dmitry Gutov
2020-06-02 17:51 ` Simen Heggestøyl
[not found] ` <87k10picej.fsf@simenheg@gmail.com>
2020-06-02 21:33 ` Dmitry Gutov
[not found] ` <5ed13064.1c69fb81.4bf5e.dc8eSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-03 11:28 ` Basil L. Contovounesios
2020-06-03 11:27 ` Basil L. Contovounesios
2020-06-03 11:47 ` Dmitry Gutov
2020-06-03 13:38 ` Basil L. Contovounesios
2020-06-03 19:15 ` Simen Heggestøyl
[not found] ` <87lfl4x8p0.fsf@simenheg@gmail.com>
2020-06-03 20:11 ` Dmitry Gutov
2020-06-04 18:19 ` Simen Heggestøyl
2020-05-29 22:55 ` Kévin Le Gouguec
2020-05-29 23:22 ` Dmitry Gutov
2020-05-29 23:31 ` Dmitry Gutov
2020-05-30 0:42 ` Dmitry Gutov
2020-05-30 6:05 ` Simen Heggestøyl
[not found] ` <5ed1f7ae.1c69fb81.9b99b.4ce7SMTPIN_ADDED_BROKEN@mx.google.com>
2020-05-30 12:42 ` Kévin Le Gouguec
2020-05-30 13:17 ` Dmitry Gutov
2020-05-30 17:05 ` Dmitry Gutov
2020-05-30 18:29 ` Kévin Le Gouguec
2020-06-02 17:29 ` Simen Heggestøyl
[not found] ` <877dwuc5zu.fsf@simenheg@gmail.com>
2020-05-30 13:21 ` Dmitry Gutov
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=87a71hvi3b.fsf@bulbul \
--to=philip@warpmail.net \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=simenheg@runbox.com \
/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).