From: YUE Daian <sheepduke@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Time to consider/try Helm?
Date: Wed, 31 Oct 2018 12:14:13 +0800 [thread overview]
Message-ID: <87d0rq3g8a.fsf@work.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87a7mv84c0.fsf@sphax>
On 2018-10-30 23:19, Rémi Letot <hobbes@poukram.net> wrote:
> YUE Daian <sheepduke@gmail.com> writes:
>
>> Hi Boris,
>>
>> For me it was from vanilla to ido to helm. Never looked back.
>>
>> There are many debates of choosing helm or ivy. Their user experience
>> might be quite different. But both of them are far better than ido
>> IMHO.
>
> Could you please elaborate a bit on that ?
>
> Thanks,
> --
> Rémi
Hi Remi,
Sorry for not being able to type the accent ;-)
I am not really familiar with ivy so please let me talk about helm.
Let's take buffer management as an example.
With ido you have `ido-switch-buffer`, `ido-kill-buffer` etc for
different purposes.
But with helm, when you use `helm-buffer-list`, it pops up a buffer,
which displays all opened and recently used buffers.
You can type anything in the mini-buffer to perform fuzzy-search and the
buffer list will be filtered.
You can mark items in the list and perform actions on them, for example
kill buffer, query replace, grep etc etc.
These actions are customizable thus can be added more.
Also packages like helm can be used as a front-end for many other tools,
such as ag (great enhancement of grep, highly recommended), projectile
etc etc.
I think the biggest change helm brings is that it uses buffer instead of
mini-buffer to display its results.
Hope that helps.
Danny
next prev parent reply other threads:[~2018-10-31 4:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 12:43 Time to consider/try Helm? Jonathon McKitrick
2018-10-29 14:48 ` Boris Buliga
2018-10-30 7:11 ` YUE Daian
2018-10-30 8:19 ` Marcin Borkowski
2018-10-30 9:21 ` Skip Montanaro
2018-10-30 10:19 ` YUE Daian
2018-10-30 10:31 ` Boris Buliga
2018-10-30 14:41 ` Eric S Fraga
2018-10-30 14:47 ` Boris Buliga
2018-10-30 14:47 ` Óscar Fuentes
[not found] ` <mailman.3102.1540910509.1284.help-gnu-emacs@gnu.org>
2018-10-30 18:11 ` Ben Bacarisse
2018-10-31 10:38 ` Eric S Fraga
2018-10-30 22:19 ` Rémi Letot
2018-10-31 4:14 ` YUE Daian [this message]
2018-10-31 10:34 ` Eric S Fraga
2018-10-31 10:57 ` Marcin Borkowski
2018-10-31 12:17 ` Eric S Fraga
2018-10-31 11:08 ` YUE Daian
2018-10-31 10:59 ` Marcin Borkowski
2018-10-31 11:23 ` YUE Daian
2018-10-31 19:03 ` Rémi Letot
2018-10-31 19:08 ` Boris Buliga
2018-11-01 19:27 ` Marcin Borkowski
2018-11-02 3:55 ` YUE Daian
2018-11-03 14:09 ` Neal Becker
2018-10-30 6:48 ` Vladimir Sedach
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=87d0rq3g8a.fsf@work.i-did-not-set--mail-host-address--so-tickle-me \
--to=sheepduke@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).