Re: A package in a league of its own: Helm

["Óscar Fuentes" <ofv@wanadoo.es>]

solidius4747@gmail.com writes:

> 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.

99.9% of the time I work on projects that I worked on previously and
hence I know its structure. Knowing the *precise* structure is not
really required as you can type just the part that is characteristic
enough (the ordering matters, though, as you mentioned.) Having a method
that minimizes the amount of text that I have to write is very
convenient.

For your query about the existence of a main.c file for the x86 arch, I
would type "x86main.c". The answer should be evident by just looking at
the first match. (Acually, "xmac" should be enough if you are willing to
look beyond the first match.)

I get your point about incrementally refining the query and I realize
that it can be more convenient than flx for certain uses (such as when
exploring a large set of previously unknown candidates.) It's only that
the flx way is more convenient on my case, where I always work on a
semi-known set of candidates.