From: Ivan Shmakov <ivan@siamics.net>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: vc-dir default directory: repository root?
Date: Thu, 22 Jan 2015 15:50:57 +0000 [thread overview]
Message-ID: <87vbjyq0f2.fsf@violet.siamics.net> (raw)
In-Reply-To: <54C10DE0.1050203@yandex.ru> (Dmitry Gutov's message of "Thu, 22 Jan 2015 16:49:04 +0200")
>>>>> Dmitry Gutov <dgutov@yandex.ru> writes:
>>>>> On 01/22/2015 04:45 PM, Ivan Shmakov wrote:
>>> And ido-find-file binds `M-n' to a totally different command.
>> … Yet it still leaves ‘down’ bound to just the same good old
>> next-line-or-history-element.
> Does it?
> ...<down> runs the command ido-next-match-dir...
> Check out the definition of ido-file-dir-completion-map.
I’m unfamiliar with ido.el, so I’ve indeed missed the
(ido-mode 'file) part.
Now, do I understand it correctly that no minibuffer history is
available with ido?
Anyway, given that vc-dir (AIUI) has never been altered by
ido-mode, and given that there’re a fair share of commands never
touched by that (M-x and M-: come to mind), I still expect for
the users to be generally familiar with the usual history
navigation commands and bindings.
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2015-01-22 15:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 6:52 vc-dir default directory: repository root? Daniel Colascione
2015-01-11 1:26 ` Stefan Monnier
2015-01-11 8:33 ` Andreas Schwab
2015-01-11 15:53 ` Wolfgang Jenkner
2015-01-11 19:02 ` Dan Nicolaescu
2015-01-19 1:40 ` Dmitry Gutov
2015-01-19 15:47 ` Dan Nicolaescu
2015-01-19 23:17 ` Dmitry Gutov
2015-01-20 20:06 ` Dan Nicolaescu
2015-01-21 14:33 ` Stefan Monnier
2015-01-21 16:20 ` Ivan Shmakov
2015-01-21 17:33 ` Dan Nicolaescu
2015-01-21 17:48 ` Dmitry Gutov
2015-01-21 18:22 ` Ivan Shmakov
2015-01-21 18:43 ` Dmitry Gutov
2015-01-21 19:22 ` Ivan Shmakov
2015-01-21 18:47 ` João Távora
2015-01-21 19:06 ` Dmitry Gutov
2015-01-21 20:14 ` João Távora
2015-01-21 20:30 ` Dmitry Gutov
2015-01-22 12:40 ` João Távora
2015-01-22 15:19 ` Dan Nicolaescu
2015-01-21 19:35 ` Wolfgang Jenkner
2015-01-21 19:42 ` Daniel Colascione
2015-01-21 20:16 ` Stefan Monnier
2015-01-22 9:59 ` Daniel Colascione
2015-01-22 1:44 ` Dmitry Gutov
2015-01-22 9:17 ` Andreas Schwab
2015-01-22 11:14 ` Dmitry Gutov
2015-01-22 12:04 ` Jan D.
2015-01-22 14:18 ` Stefan Monnier
2015-01-22 14:23 ` Dmitry Gutov
2015-01-22 14:38 ` Andreas Schwab
2015-01-22 14:46 ` Dmitry Gutov
2015-01-22 15:30 ` Drew Adams
2015-01-22 16:16 ` Dmitry Gutov
2015-01-22 15:40 ` Andreas Schwab
2015-01-22 14:45 ` Ivan Shmakov
2015-01-22 14:49 ` Dmitry Gutov
2015-01-22 15:50 ` Ivan Shmakov [this message]
2015-01-22 16:26 ` Dmitry Gutov
2015-01-22 16:11 ` Wolfgang Jenkner
2015-01-19 1:38 ` Dmitry Gutov
2015-01-19 3:01 ` Stefan Monnier
2015-01-19 4:54 ` Dmitry Gutov
2015-01-19 14:16 ` Stefan Monnier
2015-01-19 14:55 ` Dmitry Gutov
2015-01-19 14:57 ` Daniel Colascione
2015-01-19 22:43 ` 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=87vbjyq0f2.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--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).