all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: How to disable ido and icomplete in some path/directory?
Date: Tue, 19 Dec 2017 08:32:32 -0500	[thread overview]
Message-ID: <jwvh8smc0gw.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: CACspjXc1_iq_uh1+DBD-COzu9HzDepEaDTb6eppNHYRKWx0Zmg@mail.gmail.com

> 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




  reply	other threads:[~2017-12-19 13:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19  6:44 How to disable ido and icomplete in some path/directory? Shuguang Sun
2017-12-19 13:32 ` Stefan Monnier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-20  5:24 Shuguang Sun
2017-12-20 16:11 ` Stefan Monnier
2017-12-20  1:06 Shuguang Sun
2017-12-20  2:01 ` Óscar Fuentes
2017-12-19 14:57 Shuguang Sun
2017-12-19 15:11 ` Stefan Monnier
2017-12-19  2:09 Shuguang Sun
2017-12-19  3:09 ` Stefan Monnier
2017-12-18  8:44 Shuguang Sun
2017-12-18 21:59 ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvh8smc0gw.fsf-monnier+gmane.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.