From: Dmitry Gutov <dgutov@yandex.ru>
To: Stephen Leake <stephen_leake@stephe-leake.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: standard key binding for project-find-file?
Date: Mon, 2 Dec 2019 15:43:52 +0200 [thread overview]
Message-ID: <c43bcd0f-0413-c9b6-f50c-3ab1c05820fe@yandex.ru> (raw)
In-Reply-To: <86mucbne4o.fsf@stephe-leake.org>
On 02.12.2019 13:47, Stephen Leake wrote:
> C-c C-t is available, and is
> near C-c C-f
'C-c C-t' is not bad, but why not 'C-c C-f'? It's unbound, too.
next prev parent reply other threads:[~2019-12-02 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 11:47 standard key binding for project-find-file? Stephen Leake
2019-12-02 12:33 ` Robert Pluim
2019-12-02 13:43 ` Dmitry Gutov [this message]
2019-12-02 18:42 ` Alan Mackenzie
2019-12-02 19:07 ` Matthias Meulien
2019-12-02 20:52 ` Drew Adams
2019-12-03 7:09 ` Stefan Kangas
2019-12-03 20:49 ` Stephen Leake
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=c43bcd0f-0413-c9b6-f50c-3ab1c05820fe@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.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).