From: Marcin Borkowski <mbork@mbork.pl>
To: YUE Daian <sheepduke@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Time to consider/try Helm?
Date: Thu, 01 Nov 2018 20:27:10 +0100 [thread overview]
Message-ID: <87muqsiooh.fsf@mbork.pl> (raw)
In-Reply-To: <87ftwm9x6b.fsf@work.i-did-not-set--mail-host-address--so-tickle-me>
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.
> 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.
>>> 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-01 19:27 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 [this message]
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=87muqsiooh.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=sheepduke@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).