unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
	Le Wang <l26wang@gmail.com>
Subject: Re: Emacs needs truely useful flex matching
Date: Fri, 22 Mar 2013 15:18:53 +0400	[thread overview]
Message-ID: <87y5dfheci.fsf@yandex.ru> (raw)
In-Reply-To: <83a9pv6dwf.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Mar 2013 10:24:00 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 22 Mar 2013 09:00:14 +0800
>> From: Le Wang <l26wang@gmail.com>
>> Cc: Óscar Fuentes <ofv@wanadoo.es>, emacs-devel@gnu.org
>> 
>> > Indeed when searching for a file in a file hierarchy, you'd need
>> > a pre-built list of files, otherwise the time taken to find the files
>> > would dwarf the flex-matching time in any case.
>> 
>> "git ls-files" is very fast on a solid state drive, and the list can
>> also be cached.
>
> Compare "git ls-files" with "ls -R" (time-wise and also look at the
> disk activity LED, if you have one) on the same directory and machine,
> and you will see that git does not actually look at the filesystem to
> find the files.

Sure, and that means that caching the list of files a in directory tree
is a somewhat solved issue. Whereas the kind of magical flex matching Le
is describing, isn't.



  reply	other threads:[~2013-03-22 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 15:02 Emacs needs truely useful flex matching Le Wang
2013-03-21 17:49 ` Óscar Fuentes
2013-03-21 23:34   ` Le Wang
2013-03-21 23:58   ` Stefan Monnier
2013-03-22  1:00     ` Le Wang
2013-03-22  8:24       ` Eli Zaretskii
2013-03-22 11:18         ` Dmitry Gutov [this message]
2013-04-14 16:48       ` Le Wang
2013-04-14 18:18         ` Stefan Monnier
2013-04-15  0:14           ` Le Wang
2013-04-15 13:50             ` Stefan Monnier
2013-03-22  2:36 ` Richard Stallman

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=87y5dfheci.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=l26wang@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=ofv@wanadoo.es \
    /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).