Thierry Volpiatto
<
thierry....@gmail.com> writes:
> Eric Abrahamsen <
er...@ericabrahamsen.net> writes:
>
>> The help for `helm-find-files' says that I can hit "C-x C-f" a second
>> time to drop into the vanilla find-files interface.
>
> Where did you see this info, I can't find it, it is not true anyway, C-x
> C-f switch to locate.
If you hit "C-h m" while in the helm-find-files interface, the
documentation buffer still says "C-x C-f" will drop you into the basic
`find-files' interface.
>> That key seems to be currently bound to `helm-ff-run-locate', however.
>
> Yes.
>
>> I don't mind that, but it would be nice if the regular `find-files' were
>> still accessible.
>
> What you can do is disable helm completion for `find-file':
> (add-to-list 'helm-completing-read-handlers-alist '(find-file . nil))
I don't want to disable helm for find-file, I like using it! I only want
to occasionally disable it in special circumstances.
>> When accessing files on a remote server through tramp, it's *really*
>> nice not to have to fight with remote completion -- my connection is
>> just too slow.
>
> Can you develop on this, what's wrong with helm+tramp ?
I'm in China and my ssh connection to overseas servers is ghastly slow.
If I just type out the path to the file I want to edit and hit RET,
helm-find-files simply ends -- no file is opened, no error is raised. If
I want to really get the file open, I have to wait at each filepath
segment for the completion information to come back. That really takes a
long time, and its fragile: I feel like if I type anything unexpected,
the whole process quits and I have to start over.
In most cases I know what config file I'm after, and the path is short
-- I'd much rather just type out the path and get the file.
E