unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 'Leo' <sdl.web@gmail.com>, emacs-devel@gnu.org
Subject: RE: `completion-in-region'
Date: Sun, 11 Apr 2010 12:56:15 -0700	[thread overview]
Message-ID: <B8CEB0AF6C26436DA7139B1CEB8C3146@us.oracle.com> (raw)
In-Reply-To: <jwvd3y5zssk.fsf-monnier+emacs@gnu.org>

> > TextMate's default matching (it has no name AFAIK) is the same as
> > Ido's "flex" matching and Icicles's "scatter" matching. It is
> > a poor-man's fuzzy matching (not fuzzy matching in the more usual
> > sense). (TextMate uses this matching only for file names, I 
> > believe.)
> 
> I see that ido implements it by turning "abc" into the regexp
> ".*a.*b.*c".  But matching this regexp against a string like
> "abababababab" takes time O(N^3) where N is the length of the 
> completion candidate, which makes me a bit uneasy (and in
> general matching "flex"ibly an input string of size M against
> a completion candidate of size N can take time O(N^M)).  But
> I guess experience shows it's not a real problem.
> 
> It should be pretty easy to add it as a new completion-style 
> (after all you can already get the same result with partial
> completion by typing "*a*b*c").

Yes, to all you said.

The question is whether matching like this should be the default. IMO, no.





  reply	other threads:[~2010-04-11 19:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 14:37 `completion-in-region' Leo
2010-04-09  3:05 ` `completion-in-region' Stefan Monnier
2010-04-11 12:56   ` `completion-in-region' Leo
2010-04-11 15:32     ` `completion-in-region' Stefan Monnier
2010-04-11 18:05       ` `completion-in-region' Drew Adams
2010-04-11 19:44         ` `completion-in-region' Stefan Monnier
2010-04-11 19:56           ` Drew Adams [this message]
2010-04-11 20:49             ` `completion-in-region' Stefan Monnier
2010-04-11 21:13               ` `completion-in-region' Drew Adams
2010-04-11 20:08           ` `completion-in-region' Lennart Borgman
2010-04-11 20:51             ` `completion-in-region' Stefan Monnier
2010-04-11 21:06               ` `completion-in-region' Lennart Borgman
2010-04-12  2:10                 ` `completion-in-region' Stefan Monnier
2010-04-12  9:46                   ` `completion-in-region' Lennart Borgman
2010-04-12 13:10                     ` `completion-in-region' Stefan Monnier
2010-04-12 14:50                     ` `completion-in-region' Davis Herring
2010-04-11 21:12             ` `completion-in-region' Drew Adams
2010-04-12 15:36       ` `completion-in-region' Leo
2010-04-12 18:10         ` `completion-in-region' Stefan Monnier
2010-04-12 15:51       ` `completion-in-region' Leo

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=B8CEB0AF6C26436DA7139B1CEB8C3146@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sdl.web@gmail.com \
    /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).