From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs needs truely useful flex matching
Date: Thu, 21 Mar 2013 19:58:11 -0400 [thread overview]
Message-ID: <jwvwqt0wbvh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <877gl0od6x.fsf@wanadoo.es> ("Óscar Fuentes"'s message of "Thu, 21 Mar 2013 18:49:42 +0100")
>> The sorting algorithm is roughly this for a query: "abcd"
>>
>> 1. Get all matches for "a.*b.*c.*c"
>> 2. Calculate score of each match
>> - contiguous matched chars gets a boost
>> - matches at word and camelCase boundaries (abbreviation) get a boost
>> - matches with smallest starting index gets a boost
>> 2. Sort list according to score.
I think that if you turn "abcd" into a regexp of the form
"\\(\\<\\)?a\\([^b]*\\)\\(\\<\\)?b\\([^c]*\\)\\(\\<\\)?c\\([^d]*\\)\\(\\<\\)?d"
the regexp matching should be fairly efficient and you should be able to
compute the score efficiently as well (at least if
you ignore the camelCase boundaries).
>> This navigation could be implemented with Helm if Emacs had a builtin
>> fast smart flex sorting engine.
Have you tried such an approach and it really was too slow?
I'd welcome a new completion-style using the above flex matching.
> IIUC the vim plugin you mention depends on a pre-built list of files.
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.
Stefan
next prev parent reply other threads:[~2013-03-21 23:58 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 [this message]
2013-03-22 1:00 ` Le Wang
2013-03-22 8:24 ` Eli Zaretskii
2013-03-22 11:18 ` Dmitry Gutov
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=jwvwqt0wbvh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--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).