From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Tu, Do" Newsgroups: gmane.emacs.help Subject: Re: A package in a league of its own: Helm Date: Mon, 1 Sep 2014 09:43:20 -0700 (PDT) Message-ID: <66ac7656-4c1a-416b-873c-88e2bad3cf83@googlegroups.com> References: <787f8d86-dede-4627-b4e5-3658a1833455@googlegroups.com> <73520ac0-9fc0-42ce-8a15-cc400b6f8308@googlegroups.com> <672a0d66-bc48-4b7a-9279-c7d631a03f79@googlegroups.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1409589923 14504 80.91.229.3 (1 Sep 2014 16:45:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Sep 2014 16:45:23 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Sep 01 18:45:18 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XOUjG-00027v-K5 for geh-help-gnu-emacs@m.gmane.org; Mon, 01 Sep 2014 18:45:18 +0200 Original-Received: from localhost ([::1]:33000 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOUjG-0002SM-7K for geh-help-gnu-emacs@m.gmane.org; Mon, 01 Sep 2014 12:45:18 -0400 X-Received: by 10.236.11.80 with SMTP id 56mr6256702yhw.22.1409589801354; Mon, 01 Sep 2014 09:43:21 -0700 (PDT) X-Received: by 10.50.57.113 with SMTP id h17mr479240igq.0.1409589801250; Mon, 01 Sep 2014 09:43:21 -0700 (PDT) Original-Path: usenet.stanford.edu!dc16no307067qab.1!news-out.google.com!aw9ni2087igc.0!nntp.google.com!r2no12190626igi.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=14.161.13.65; posting-account=c2AWuQoAAACA36o69JJJEmXY5MOg4YNp Original-NNTP-Posting-Host: 14.161.13.65 User-Agent: G2/1.0 Injection-Date: Mon, 01 Sep 2014 16:43:21 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:207287 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:99564 Archived-At: @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 se= arch for any file in your project, you have to use Projectile: https://gith= ub.com/bbatsov/projectile If you don't use Projectile, Ido won't be able to any file in your director= y either. V=C3=A0o 23:01:22 UTC+7 Th=E1=BB=A9 hai, ng=C3=A0y 01 th=C3=A1ng ch=C3=ADn = n=C4=83m 2014, Phil Lord =C4=91=C3=A3 vi=E1=BA=BFt: > First, thanks for the tutorial. I've tried helm (and anything) several >=20 > times, but never got on with it as I have found the experience too >=20 > confusing. I've always reverted to ido. I like the idea of helm because >=20 > it is more pervasive than ido and can do several things at once. I >=20 > dislike the practice of helm because too many things happen at once (and >=20 > the wiki is incomprehensible). >=20 >=20 >=20 > The thing that I am stuck on at the moment, is file navigation. With >=20 > ido.el, I use [tab] or [del] to move up or down directories (and carry >=20 > on selecting). With helm I have to use C-l C-j which I find much slower >=20 > because of the double keypress and because C-k is in the middle. >=20 >=20 >=20 > I don't get the behaviour you are talking about with helm. I get a >=20 > single directory at once, and I have to navigate through it to get to >=20 > the files I want. >=20 >=20 >=20 > Clearly I doing something wrong! >=20 >=20 >=20 > Phil >=20 >=20 >=20 >=20 >=20 >=20 >=20 > writes: >=20 > > Consider this path: arch/x86/boot/main.c >=20 > > >=20 > > Can you type the file name first: "main.c", then add "x86" to get the c= orrect >=20 > > file above? I'm pretty sure ido+flx can't do that, but maybe I'm missin= g >=20 > > something. >=20 > > >=20 > > With Helm, you can simply specify "mai x86" and it narrows to 3 candida= tes >=20 > > with the above path at the top. The file is in Linux kernel source. >=20 > > >=20 > > Maybe you misunderstood my statement about precise remembering project >=20 > > structure. What I meant was you have to remember the correct path order= ing, >=20 > > and that requires you to be familiar with the directory structure. Whli= e in >=20 > > Helm, I'm completely new to a directory and simply know nothing about >=20 > > directory structure. With Helm, I can start pop up questions like "is t= here a >=20 > > main.c that is relate to x86 arch?" and so on. >=20 > > >=20 > > >=20 >=20 >=20 > --=20 >=20 > Phillip Lord, Phone: +44 (0) 191 222 7827 >=20 > Lecturer in Bioinformatics, Email: phillip.lord@newcastle.ac.= uk >=20 > School of Computing Science, http://homepages.cs.ncl.ac.uk/phi= llip.lord >=20 > Room 914 Claremont Tower, skype: russet_apples >=20 > Newcastle University, twitter: phillord >=20 > NE1 7RU