all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / 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: Wed, 03 Sep 2014 11:43:17 +0100	[thread overview]
Message-ID: <87k35lvvay.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <75ba2f61-8bff-41dd-aee5-6ce99cedd9d7@googlegroups.com> (Do Tu's message of "Tue, 2 Sep 2014 07:32:12 -0700")

"Tu, Do" <solidius4747@gmail.com> writes:
>> 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.
>>
>
> For an edge case like that where everything is at the top, then even stock
> find-file is fast. 


This is not an edge case for me. I have a lot of empty directories. In
the ideal world ido or helm would just squash them.


> But then, your current directory contains many files then you may one
> to look around to see the files in that directory. In that case, Ido
> cannot do it because you cannot have an actually buffer to scroll
> up/down to see. In this case, with Ido, you have to drop into Dired,
> look around and start ido-find-file again.


Yes, this is true, if the number of files is large. For small numbers
you can see the options, for large numbers this is truncated.

>> 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
>
> helm-projectile is really nice but if you want to look at the current
> directory or navigate around, you should use helm-find-files. C-j means that
> you proceed to the next level, that is either a file or a directory. Hit 1
> means pressing one time. Hit 2 means pressing 2 times; pres you hit C-j twices
> and if your highlighting is on a file, then the file content is opened up in
> another buffer. You can also press C-u in helm-find-files; its has the same
> effect as pressing C-j twice. You can navigate the other buffer with
> M-<next>/M-<prior>.


Okay, that's a good explanation!



> Actually, navigating back and forth with C-j/C-l is much faster than <tab> and
> <delete>/<return> since both of those keys are on the home row.

Well, we both having the confounding factor that I am used to
del/tab/ret and you are used to C-j/C-l. None the less, I would argue
that single key presses are faster than doubles, especially for
tab/del/retn which everyone uses a lot and are nice and big.

Phil




  reply	other threads:[~2014-09-03 10:43 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
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 [this message]
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=87k35lvvay.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.
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.