all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: YUE Daian <sheepduke@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Time to consider/try Helm?
Date: Tue, 30 Oct 2018 15:11:25 +0800	[thread overview]
Message-ID: <87a7mvlxia.fsf@work.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAD5F_-BB-oRgG=89irjsMdZ9xtWJXcJshZVa6tzu16B03m79Xw@mail.gmail.com>

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.

My suggestion is you may try both and see which you like.

As a helm user I would remind you that the behavior of <tab> can be
customized...

Danny

On 2018-10-29 16:48, Boris Buliga <boris@d12frosted.io> wrote:
> Hi Jonathon,
>
> For me it was a leap from ido to helm and then to ivy (counsel, swiper).
> Not looking back at all.
>
> But helm definitely worth giving it a try.
>
> On Mon, 29 Oct 2018 at 14:45, Jonathon McKitrick <jmckitrick@gmail.com>
> wrote:
>
>> I've been using emacs for nearly 20 years, and I try to update my packages
>> and config regularly to improve usability and incorporate current
>> development techniques.
>>
>> I went from IDO a few years ago to counsel and swiper. I've been hearing a
>> lot about Helm, and I'm wondering if it's a revolutionary leap I should
>> try, or an evolutionary step that isn't worth relearning my habits around.
>>
>> Does anyone have any similar experience with ido/counsel/helm?
>>
>>
>
> -- 
> Cheers,
> Boris



  reply	other threads:[~2018-10-30  7:11 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 [this message]
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
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=87a7mvlxia.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.
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.