From: solidius4747@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: A package in a league of its own: Helm
Date: Fri, 29 Aug 2014 10:08:23 -0700 (PDT) [thread overview]
Message-ID: <672a0d66-bc48-4b7a-9279-c7d631a03f79@googlegroups.com> (raw)
In-Reply-To: <mailman.7852.1409330926.1147.help-gnu-emacs@gnu.org>
>
> Okay. I have a different view here (and your description of flx
>
> requiring to precisely remenbering the structure of your target is not
>
> accurate, in my experience.) I would never switch from ido+flx if the
>
> alternative does nor provide the same fuzzy matching capabilities. After
>
> investigating a bit, the bad news is that incorporating flx into helm is
>
> not easy at all. The good news is that there are a significant interest
>
> on doing it, including flx's author. Let's see how this evolves.
>
>
>
> Thanks for answering my questions.
Consider this path: arch/x86/boot/main.c
Can you type the file name first: "main.c", then add "x86" to get the correct file above? I'm pretty sure ido+flx can't do that, but maybe I'm missing something.
With Helm, you can simply specify "mai x86" and it narrows to 3 candidates with the above path at the top. The file is in Linux kernel source.
Maybe you misunderstood my statement about precise remembering project structure. What I meant was you have to remember the correct path ordering, and that requires you to be familiar with the directory structure. Whlie in Helm, I'm completely new to a directory and simply know nothing about directory structure. With Helm, I can start pop up questions like "is there a main.c that is relate to x86 arch?" and so on.
next prev parent reply other threads:[~2014-08-29 17:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 4:18 A package in a league of its own: Helm solidius4747
2014-08-29 5:49 ` Guide for package use?(was A package in a league of its own: Helm) Rusi
2014-08-29 6:17 ` solidius4747
2014-08-29 13:36 ` A package in a league of its own: Helm Óscar Fuentes
[not found] ` <mailman.7830.1409319420.1147.help-gnu-emacs@gnu.org>
2014-08-29 14:03 ` solidius4747
2014-08-29 15:06 ` solidius4747
2014-08-29 16:48 ` Óscar Fuentes
[not found] ` <mailman.7852.1409330926.1147.help-gnu-emacs@gnu.org>
2014-08-29 17:08 ` solidius4747 [this message]
2014-08-29 18:03 ` Óscar Fuentes
[not found] ` <mailman.7861.1409335444.1147.help-gnu-emacs@gnu.org>
2014-08-30 1:49 ` solidius4747
2014-08-30 3:33 ` Óscar Fuentes
[not found] ` <mailman.7892.1409369651.1147.help-gnu-emacs@gnu.org>
2014-08-30 3:55 ` solidius4747
2014-09-01 16:01 ` Phillip Lord
2014-09-01 16:49 ` York Zhao
2014-09-02 13:06 ` Phillip Lord
[not found] ` <mailman.8044.1409590146.1147.help-gnu-emacs@gnu.org>
2014-09-01 16:59 ` Tu, Do
2014-09-01 17:25 ` Nikolai Weibull
2014-09-01 17:28 ` Óscar Fuentes
2014-09-01 17:40 ` York Zhao
2014-09-01 20:37 ` Michael Heerdegen
2014-09-02 0:27 ` York Zhao
2014-09-02 1:40 ` Eric Abrahamsen
2014-09-02 1:56 ` York Zhao
2014-09-02 23:15 ` Tak Kunihiro
[not found] ` <mailman.8046.1409592357.1147.help-gnu-emacs@gnu.org>
2014-09-02 8:21 ` Tu, Do
2014-09-02 13:27 ` Phillip Lord
[not found] ` <mailman.8039.1409587302.1147.help-gnu-emacs@gnu.org>
2014-09-01 16:43 ` Tu, Do
2014-09-02 13:19 ` Phillip Lord
2014-09-02 14:13 ` York Zhao
2014-09-02 14:20 ` Phillip Lord
2014-09-02 17:03 ` York Zhao
2014-09-03 9:58 ` Phillip Lord
[not found] ` <mailman.8183.1409738348.1147.help-gnu-emacs@gnu.org>
2014-09-03 10:19 ` Tu, Do
[not found] ` <mailman.8134.1409677438.1147.help-gnu-emacs@gnu.org>
2014-09-02 17:11 ` Tu, Do
2014-09-02 17:32 ` York Zhao
2014-09-02 18:15 ` Tu
2014-09-03 0:35 ` York Zhao
[not found] ` <mailman.8166.1409704538.1147.help-gnu-emacs@gnu.org>
2014-09-03 3:50 ` Tu, Do
[not found] ` <mailman.8106.1409664004.1147.help-gnu-emacs@gnu.org>
2014-09-02 14:32 ` Tu, Do
2014-09-03 10:43 ` Phillip Lord
2014-08-31 9:09 ` Ernesto Durante
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=672a0d66-bc48-4b7a-9279-c7d631a03f79@googlegroups.com \
--to=solidius4747@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.
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.