unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: "Tu\, Do" <solidius4747@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: A package in a league of its own: Helm
Date: Tue, 02 Sep 2014 14:19:52 +0100	[thread overview]
Message-ID: <87ha0qb1mv.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <66ac7656-4c1a-416b-873c-88e2bad3cf83@googlegroups.com> (Do Tu's message of "Mon, 1 Sep 2014 09:43:20 -0700")


I could rebind helm to make it use tab and delete like ido, although I
think it would still not be as nice as ido. Say I do find-file in a
directory, then select src, then uk, then ac, then ncl (as in a java
project), in ido I go C-xC-f s [rtn][rtn][rtn][rtn] because ido offers
"uk" and the others as the first completion. Helm offers "." and ".." as
the first two, so I have to do C-xCf s
[right][down][down][right][down][down][right]. Or I have to hit the
first key of "uk", then "ac" -- all of which requires thinking about.

I've been using projectile, but with ido -- this is what is giving you
the completion you show?

Well, I am writing. Across the top of the helm-find-file session, my
buffer says:

C-j: Hit1 Expand Candidate, Hit2 or (C-u) Find file
find-file (`C-l': Go up one level)

What does "Hit1" and "Hit2" mean?

Phil




"Tu, Do" <solidius4747@gmail.com> writes:

> @Ernesto I'm glad you find it helpful. I hope you enjoy Helm :)
>
> @Phil
>
> You should follow the configuration in my guide and swap TAB and C-z. Then,
> you can press TAB for entering directory. C-l is used to go back to parent
> directory, it requires two key pressed but it is closer to the home row. I
> don't think it's much slower. I find it actually faster. If you want to search
> for any file in your project, you have to use Projectile:
> https://github.com/bbatsov/projectile
>
> If you don't use Projectile, Ido won't be able to any file in your directory either.
>
> Vào 23:01:22 UTC+7 Thứ hai, ngày 01 tháng chín năm 2014, Phil Lord đã viết:
>> First, thanks for the tutorial. I've tried helm (and anything) several
>> 
>> times, but never got on with it as I have found the experience too
>> 
>> confusing. I've always reverted to ido. I like the idea of helm because
>> 
>> it is more pervasive than ido and can do several things at once. I
>> 
>> dislike the practice of helm because too many things happen at once (and
>> 
>> the wiki is incomprehensible).
>> 
>> 
>> 
>> The thing that I am stuck on at the moment, is file navigation. With
>> 
>> ido.el, I use [tab] or [del] to move up or down directories (and carry
>> 
>> on selecting). With helm I have to use C-l C-j which I find much slower
>> 
>> because of the double keypress and because C-k is in the middle.
>> 
>> 
>> 
>> I don't get the behaviour you are talking about with helm. I get a
>> 
>> single directory at once, and I have to navigate through it to get to
>> 
>> the files I want.
>> 
>> 
>> 
>> Clearly I doing something wrong!
>> 
>> 
>> 
>> Phil
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> <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.
>> 
>> >
>> 
>> >
>> 
>> 
>> 
>> -- 
>> 
>> Phillip Lord,                           Phone: +44 (0) 191 222 7827
>> 
>> Lecturer in Bioinformatics,             Email: phillip.lord@newcastle.ac.uk
>> 
>> School of Computing Science,            http://homepages.cs.ncl.ac.uk/phillip.lord
>> 
>> Room 914 Claremont Tower,               skype: russet_apples
>> 
>> Newcastle University,                   twitter: phillord
>> 
>> NE1 7RU
>
>
>

-- 
Phillip Lord,                           Phone: +44 (0) 191 222 7827
Lecturer in Bioinformatics,             Email: phillip.lord@newcastle.ac.uk
School of Computing Science,            http://homepages.cs.ncl.ac.uk/phillip.lord
Room 914 Claremont Tower,               skype: russet_apples
Newcastle University,                   twitter: phillord
NE1 7RU                                 



  reply	other threads:[~2014-09-02 13:19 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
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 [this message]
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=87ha0qb1mv.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=help-gnu-emacs@gnu.org \
    --cc=solidius4747@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.
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).