all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hans BKK <hansbkk@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Helm (and?) or Icicles (possibly using Evil)
Date: Wed, 23 Apr 2014 06:20:16 -0700 (PDT)	[thread overview]
Message-ID: <4cd079bd-9978-422f-9449-51d8fbe76485@googlegroups.com> (raw)

I'm looking feedback on these from those (perhaps few?) that have actually become somewhat familiar with both. Since EmacsWiki has so much information on Icicles (thanks Drew!) there isn't any need to give an overview/run-through on that package, but I haven't seen so much on Helm, just a lot of side-mentions on how fantastic it is from people whose opinion would seem to carry a lot of weight.

For example, does Helm actually help you learn how to use regexp?

Has anyone tried running both together? or is the overlap so great they interfere with each other as with icicles and ido?

My current context is facilitating exploring the "self-documentation" aspect of emacs, searching/browsing/jumping between info docs and other sources of help docs and the relevant source code.

I also plan to use emacs straight off for org-mode, shell usage and files management. Actual coding myself will come later, but is of course very relevant. Mostly web dev to start, but I want to get to know Python to start with and then Haskell, and plan to use pandoc to convert language/framework-specific docs to gnu info wherever possible, and to try to make my own code self-documenting as with elisp.

Does Helm have any support for creating info "books" as does icicles?

Drew, do you happen to know if your "Help Plus" libs are compatible/helpful with Helm's approach?


It's also possible I'll be learning emacs editing in evil mode, except in modes where there are still conflicts (apparently few these days), so feedback on that aspect is also welcome, apparently Helm's fine there.

I've stuck with del.icio.us since beta, over 20K bookmarks there, so Helm's support there as a platform for creating a DAG tree from that (self-documenting brain activity) is a tempting little project:
http://www.emacswiki.org/emacs-en/helm-delicious.el


             reply	other threads:[~2014-04-23 13:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 13:20 Hans BKK [this message]
2014-04-23 15:59 ` Helm (and?) or Icicles (possibly using Evil) Drew Adams
2014-04-24  2:51 ` Hans BKK
2014-04-24 13:53   ` Drew Adams
2014-04-24 17:48   ` Thien-Thi Nguyen
     [not found]   ` <mailman.11.1398388920.1147.help-gnu-emacs@gnu.org>
2014-04-25 16:17     ` Emanuel Berg
2014-04-27 20:09   ` Michael Heerdegen
2014-04-28 13:45     ` Le Wang
2014-04-28 14:05       ` Michael Heerdegen
2014-04-26 21:31 ` Hans BKK
2014-04-26 22:38   ` Emanuel Berg
2014-04-26 22:58   ` Emanuel Berg
2014-04-28 11:06 ` Hans BKK
2014-04-28 13:52   ` Michael Heerdegen
2014-04-28 15:45 ` Hans BKK
2014-04-28 15:53 ` Hans BKK
2014-04-28 23:07   ` Emanuel Berg

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=4cd079bd-9978-422f-9449-51d8fbe76485@googlegroups.com \
    --to=hansbkk@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.