unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Les Harris <me@lesharis.com.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: What completion mechanisms are you using?
Date: Sat, 31 Jan 2009 03:42:17 -0800	[thread overview]
Message-ID: <vuCdnZlphcSJpBnUnZ2dnUVZ_rXinZ2d@giganews.com> (raw)
In-Reply-To: beaca002-80a6-4ccf-a382-ab2266c31a63@t26g2000prh.googlegroups.com

senny <yves.senn@gmail.com> writes:

> Because I have no clue where to start searching for the ones I like, i
> wanted to ask you what extensions you are using and how they help you
> to optimize your day to day work.

I'm a big fan icicles. It adds completion for pretty much any minibuffer
related activity you can think of (and then some).  I still haven't come
close to really utilizing it to it's full potential (but then, with
emacs in general that is a rather normal state of affairs for me!)

Features that I use often would include:
 * Regex and Fuzzy matching.  These are great when I have a general idea
 what something I'm looking for is named but not exactly.  Also good for
 exploring possibilities within a subset of functionality.

 * Saving completion lists to act as de facto file listings for
   projects.
 
 * Using it's completion to enhance the discoverability of emacs
   commands for myself.

Icicles if sort of a kitchen sink solution but a high quality one.  If
you would like something a bit more focused perhaps look into ido-mode?

My two cents at any rate.

-- 
Do they only stand
By ignorance, is that their happy state,
The proof of their obedience and their faith?


  reply	other threads:[~2009-01-31 11:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 11:06 What completion mechanisms are you using? senny
2009-01-31 11:42 ` Les Harris [this message]
2009-02-01  1:30   ` Samuel Wales
2009-02-01 10:06   ` Christian Engels
2009-02-01 12:52   ` Christian Engels
2009-02-01 16:09     ` Drew Adams
2009-02-01 18:43       ` Christian Engels
     [not found]         ` <002501c984af$d8818580$0200a8c0@us.oracle.com>
2009-02-01 22:43           ` Samuel Wales
2009-02-01 23:33             ` Drew Adams
2009-02-01 23:57               ` Samuel Wales
2009-02-02  0:37               ` Samuel Wales
2009-02-02  0:24           ` Drew Adams
     [not found]           ` <mailman.6468.1233534260.26697.help-gnu-emacs@gnu.org>
2009-02-02  0:41             ` Richard Riley

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=vuCdnZlphcSJpBnUnZ2dnUVZ_rXinZ2d@giganews.com \
    --to=me@lesharis.com.invalid \
    --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).