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 18:49:52 -0700 (PDT) [thread overview]
Message-ID: <d72abf98-e08e-489d-a7e3-24777306f146@googlegroups.com> (raw)
In-Reply-To: <mailman.7861.1409335444.1147.help-gnu-emacs@gnu.org>
> 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.
Since I started using Helm, I never bother to remember the structure of my working directory. And that's the point: I don't have to remember such trivial details and I can focus my mind on other more important things.
>
> 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.)
And what if it doesn't exist? You will have to move point at the beginning and delete whole thing. With ido, you are constrained by its ordering: you cannot immediately enter what you directly one, such as an arbitrary file, and refine later. If there are a large pool of candidates, you have to move point at the beginning and start typing additional information. Worse, you maybe to move point to type something in between. Suddenly it's not so convenient to find something anymore. And ido is not particularly suit for narrowing large set of candidates with complex query.
Here is another example that make sure of Helm interface nicely: helm-semantic-or-imenu. Demo: http://tuhdo.github.io/static/part3/helm-semantic-or-imenu.gif
You can think of it as an outline tree in regular IDE, but Helm makes it interactive, and fast. I can ask question like "is there something that is function and has int in it that the function name contains memory?".
Here is another demo on Helm's homepage: https://github.com/emacs-helm/helm#advanced-usage
Finally, the strings in Helm are not just strings; they are regexp and I think they are more powerful then normal fuzzy matcher.
>
> 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.
Sure, it could be more productive for things you work regularly. But I like a general interface that can deal with both known and unknown environment.
next prev parent reply other threads:[~2014-08-30 1:49 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
2014-08-29 18:03 ` Óscar Fuentes
[not found] ` <mailman.7861.1409335444.1147.help-gnu-emacs@gnu.org>
2014-08-30 1:49 ` solidius4747 [this message]
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
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=d72abf98-e08e-489d-a7e3-24777306f146@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.
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).