From: YUE Daian <sheepduke@gmail.com>
To: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Time to consider/try Helm?
Date: Tue, 30 Oct 2018 18:19:55 +0800 [thread overview]
Message-ID: <877ehzlos4.fsf@work.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CANc-5Uy+xpha07wRVsjxufDxyCAAqx3iy=LUb9mcntB3Mdf9Sg@mail.gmail.com>
On 2018-10-30 04:21, Skip Montanaro <skip.montanaro@gmail.com> wrote:
>>
>> My journey was vanilla -> Ido -> Icicles -> Ivy.
>>
>
> Completely naive question, but what do these packages provide? I've been
> using Emacs for 30+ years and I've never heard of any of them. I guess I
> need to get out more.
>
> Skip Montanaro
These packages are "completion frameworks".
For example with helm, when you hit `M-x` and type something, it pops up
a buffer and list all possible matched commands, from which you may
select or do more actions.
The same process applies to other operations, including but not limited
to `C-x C-f`, `C-h v` etc etc.
Some helm extensions provides more interfaces for interacting with `ag`,
`locate` etc etc.
In a word, they change the way Emacs provides completion selections.
IMHO they are great packages that highly improve efficiency when you
need to search/query/complete anything inside Emacs.
Danny
next prev parent reply other threads:[~2018-10-30 10:19 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 [this message]
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
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=877ehzlos4.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).