From: YUE Daian <sheepduke@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Time to consider/try Helm?
Date: Fri, 02 Nov 2018 11:55:43 +0800 [thread overview]
Message-ID: <87sh0k3zgg.fsf@work.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87muqsiooh.fsf@mbork.pl>
On 2018-11-01 20:27, Marcin Borkowski <mbork@mbork.pl> wrote:
> On 2018-10-31, at 12:23, YUE Daian <sheepduke@gmail.com> wrote:
>
>>> Ivy can do these things, too.
>>
>> Sure. And dramatically after I tried Ivy since yesterday, I have already
>> uninstalled helm...
>
> Wow, that escalated quickly.
>
You know, since everyone here recommends Ivy I was really curious about
it. And after trying it I think it is really good :-D
>> Thank you guys, for helping me find a new tool that suits my taste more.
>
> As someone who used both Helm and Ivy, could you summarize the key
> differences? I don't think I'm going to switch to Helm;-), but I'm just
> curious.
>
Sure.
Both are excellent and I think the choice between them more likes
personal taste.
- Complexity. Helm defines a set of operation logic while Ivy completes
your habit in Emacs life. For example by default <tab> is used as
invoke-action instead of performing completion in Helm. You have to
configure much to make it behave in the way you like.
- Helm is more integrated. It contains literally every single bit of
Emacs functions, e.g. calculator. On the contrary Ivy is more
distributed thus feels more light-weight. IMO it is really funny to
integrate calculator in Helm.
- Helm uses buffer to display its information, while Ivy uses
mini-buffer. This may lead to very different experience. Sometimes C-g
cannot fully quit current operation in Helm because the usage of
window. This problem never happens in my (limited) Ivy life.
- Speed. My brief feeling is that Helm is slower most of the time, but
helm-ag rocks counsel-ag really hard. Also when dealing with very
large repo, helm-projectile is far more faster than
counsel-projectile. But maybe it is because I am using wrong regex
engine, I am not sure.
These are just some most significant feelings I have after switched to
Ivy. I believe there are more along with my Ivy life...
>>>> I think the biggest change helm brings is that it uses buffer instead of
>>>> mini-buffer to display its results.
>>>
>>> How is that beneficial? (I don't claim it isn't - I just don't know
>>> what are the pluses.)
>>
>> Here "change" is a neutral word.
>>
>> Some people like it, some people don't.
>>
>> Some people say that using an individual buffer may display more
>> information, such as file size, directory etc for buffer list.
>>
>> IMHO most information is not really needed (by me).
>>
>> So personally I could accept it, but I don't miss it after switching to
>> Ivy.
>
> I see.
>
> Thanks,
>
> --
> Marcin Borkowski
> http://mbork.pl
next prev parent reply other threads:[~2018-11-02 3:55 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh0k3zgg.fsf@work.i-did-not-set--mail-host-address--so-tickle-me \
--to=sheepduke@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/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.