From: senny <yves.senn@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: How to speed up ido?
Date: Sat, 17 Jan 2009 01:37:03 -0800 (PST) [thread overview]
Message-ID: <79524ccc-94bf-4511-bf0f-3a81337f08a7@r10g2000prf.googlegroups.com> (raw)
Hey there
I wrote a function to open any file in my project using ido. The
Problem is, that the project has a lot of files and a deeply nested
directory structure. When i then complete the file name in ido using
fuzzy-matching it is extremely slow and unusable. Is there a way to
increase the speed of ido? or should i take another approach to this
problem? I am currently using the method "ido-completing-read".
regards,
Senny
next reply other threads:[~2009-01-17 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 9:37 senny [this message]
2009-01-17 11:13 ` How to speed up ido? Andreas Politz
2009-01-17 12:48 ` Seweryn Kokot
[not found] ` <mailman.5113.1232196142.26697.help-gnu-emacs@gnu.org>
[not found] ` <1232197162.491902@arno.fh-trier.de>
[not found] ` <1232197823.618527@arno.fh-trier.de>
2009-01-17 14:18 ` senny
2009-01-17 17:26 ` Seweryn Kokot
2009-01-18 11:06 ` Andreas Politz
2009-02-17 14:13 ` David Combs
2009-01-17 15:04 ` William Xu
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=79524ccc-94bf-4511-bf0f-3a81337f08a7@r10g2000prf.googlegroups.com \
--to=yves.senn@gmail.com \
--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.
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).