How to disable ido and icomplete in some path/directory?

How to disable ido and icomplete in some path/directory?

[Shuguang Sun]

Hi,

I have ido-everywhere, icomplete-mode, and ido-mode in my init. I want to
disable ido and icomplete in some path or directory, for example, i:/work/,
when I find file, copy file (dired-do-copy), or rename file
(dired-do-rename).

Any suggestion will be appreciated.

Best Regards,
Shuguang

Re: How to disable ido and icomplete in some path/directory?

[Stefan Monnier]

> I have ido-everywhere, icomplete-mode, and ido-mode in my init. I want to
> disable ido and icomplete in some path or directory, for example, i:/work/,
> when I find file, copy file (dired-do-copy), or rename file
> (dired-do-rename).

Could you give us some hint about why you want to disable icomplete and
ido there (I wonder how they work together, by the way)?


        Stefan

Re: How to disable ido and icomplete in some path/directory?

[Shuguang Sun]

Hi Stefen,

I works on Windonw 7 and has a network driver i: (that is, I mapped a net
work location [server \\host\path\] to local). The network is very slow.
When I want to dired-do-find/copy, it takes a long time for ido/icomplete
to read the list of filenames from the server. Thereby, I want to disable
ido and icomplete in such drivers/paths.
For dired-do-find-file, I can enter edit mode by C-e, however, it does't
solve all problems, and still has very slow response at the begining and
end.

In those local driver, it is fast for ido/icomplete to read the list of
finames for completion and it is helpful.

Best Regards,
Shuguang

Re: How to disable ido and icomplete in some path/directory?

[Stefan Monnier]

> For dired-do-find-file, I can enter edit mode by C-e,

Seems like you're using IDO rather than icomplete there, then
(icomplete doesn't have an "edit mode").

> In those local driver, it is fast for ido/icomplete to read the list of
> finames for completion and it is helpful.

The way icomplete is implemented it should (in theory) not block you
from typing further while building the completion list.  AFAICT, this
also applies to IDO.  So have you tried to "keep typing" when Emacs
seems to be waiting for the network to reply?  If so, does Emacs keep
waiting, or does it "immediately" process your key (and starts trying
to build the next list of completions)?
If it keeps you waiting, then it's a bug which I suggest you report with
`M-x report-emacs-bug`.


        Stefan

Re: How to disable ido and icomplete in some path/directory?

[Shuguang Sun]

Hi Stefen

It is not a bug. Emacs will "immediately" process my key, and start trying
to building the next list of completions.
However, the network is slow, thereby, the response of emacs is delayed. It
is why I want to disable IDO/icomplete in some directory.


You remind me. I try to enable ido and icomplet separately.
The icomplete-mode trigger my issue. It tries to buidling the list after
each key typing.
The ido-everywhere just takes some times for the first time under a
directory, and don't re-read the list after each typing.


Best Regards,
Shuguang

Re: How to disable ido and icomplete in some path/directory?

[Stefan Monnier]

> It is not a bug. Emacs will "immediately" process my key, and start trying
> to building the next list of completions.
> However, the network is slow, thereby, the response of emacs is delayed.

Could you clarify here which response is delayed (since you said above
that Emacs "immediately" processes the key).

Normally, what should happen (barring bugs) is:

- let's say you're in a prompt like "Find file: /foo/bar/"
  where /foo/bar is a "slow" directory.
- Emacs is busy trying to get the list of completions.
- you hit "t"
- Emacs promptly stops trying to get the list of completions, and
  updates the minibuffer to: "Find file: /foo/bar/t"
- it then (re)tries to get the list of completions.

So if the list of completions takes too much time, it should behave
pretty much identically to what happens with icomplete disabled (I'm
talking abut icomplete here, not sure what ido would do).


        Stefan

Re: How to disable ido and icomplete in some path/directory?

[Shuguang Sun]

It is not a bug. It behave as

- let's say you're in a prompt like "Find file: /foo/bar/"
  where /foo/bar is a "slow" directory.
- Emacs is busy trying to get the list of completions.
- you hit "t"
- Emacs promptly stops trying to get the list of completions, and
  updates the minibuffer to: "Find file: /foo/bar/t"
- it then (re)tries to get the list of completions.

it is due to the slow net rate. So disable icomplete will solve the problem.

My question is how to diable ido and icomplete in some path/directory.


(Sorry it does not work to call gmail repsoning the help maillist in firefox).

Best Regards,

Shuguang

Re: How to disable ido and icomplete in some path/directory?

[Stefan Monnier]

> It is not a bug. It behave as
> - let's say you're in a prompt like "Find file: /foo/bar/"
>   where /foo/bar is a "slow" directory.
> - Emacs is busy trying to get the list of completions.
> - you hit "t"
> - Emacs promptly stops trying to get the list of completions, and
>   updates the minibuffer to: "Find file: /foo/bar/t"
> - it then (re)tries to get the list of completions.

> it is due to the slow net rate.

What is "it".

> So disable icomplete will solve the problem.

Which part of the behavior described above is the problem you want to solve?


        Stefan

Re: How to disable ido and icomplete in some path/directory?

[Shuguang Sun]

Someone uses the help maillist to train robot?

Re: How to disable ido and icomplete in some path/directory?

[Óscar Fuentes]

Shuguang Sun <shuguang@gmail.com> writes:

> Someone uses the help maillist to train robot?

:-)

IIUC Stefan is saying that the slow responsiveness of the remote network
should not matter because Emacs builds the completion list
asynchronously (at least when icomplete is used, AFAIK ido needs to
build the list before interacting with the user). If, when using
icomplete, you are forced to wait, it is a bug in Emacs. Stefan is
trying to know the exact problem you experience (with icomplete).

For ido, which builds its list of candidates synchronously, you can
advice the function `ido-is-slow-ftp-host'. This function takes a
parameter which corresponds to a directory (if this parameter is nil
then the current directory is assumed). When this function returns
non-nil, ido is disabled.

Re: How to disable ido and icomplete in some path/directory?

[Shuguang Sun]

I apolygize for my attitude. I'm in the busy timeline work now and can't
help too much on the "bug" thing.

My need is to disable ido and icomplete in some path/directory as the
title. Automatically, not manually each time.
It will be fine for me.

Something may help for bug idendification:
When I press a key in dired-do-find-file/copy/rename, then emacs hangs for
while (may be re-reading the file name list from remote and building
completion list.) Then the key shows in the minibuffer with the completion
list.
If I type two keys continously, emacs hangs for while, and then the two
keys show in the minibuffer with the completion list.


Another thing not relevant:
In the slow rate net work (net driver mapping in windows, not tramp),
fontifyiing a big buffer associated with remote file will take longer time
than local file.

Best Regards,
Shuguang

Re: How to disable ido and icomplete in some path/directory?

[Stefan Monnier]

> Something may help for bug idendification:
> When I press a key in dired-do-find-file/copy/rename, then emacs hangs for
> while (may be re-reading the file name list from remote and building
> completion list.) Then the key shows in the minibuffer with the completion
> list.
> If I type two keys continously, emacs hangs for while, and then the two
> keys show in the minibuffer with the completion list.

Ah, thanks, I see.  So that's indeed a bug.  I'll try and take a look
at it.  The key you pressed should appear *before* the completion list.


        Stefan