unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Will O'Brien" <will.08rien@gmail.com>
To: Robert Thorpe <rt@robertthorpeconsulting.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Moving from Ido to Icicles
Date: Sat, 1 Nov 2014 23:35:09 +0000	[thread overview]
Message-ID: <CAKgE0sCOKPLx_ez8fY823wV0fTDJ6vM5J7aQoNQB0_49fg87wg@mail.gmail.com> (raw)
In-Reply-To: <87a94a634q.fsf@robertthorpeconsulting.com>

On 1 Nov 2014 21:08, "Robert Thorpe" <rt@robertthorpeconsulting.com> wrote:
>
> Dale Snell <ddsnell@frontier.com> writes:
> > I can't speak for Icicles, I've never used it.  Besides, that's Drew's
> > job.  :-)  However, you might want to look into "recentf", which is a
> > built-in package.  It keeps a list of the <n> most recently opened
> > files.  The value of <n> defaults to sixteen, as I recall, but it
> > can be changed.  When you access the list (from the menu bar or from C-x
> > C-r) it presents you with that list.  You can then select the file
> > you want to open.  I've found it quite handy.
>
> There's more than one way to skin a cat.  I tend to use bookmarks with
> short names, e.g. "TR", "L", etc. for the files I access most often.
> That's not practical for something like a programming project.  For
> cases like that you can bookmark the dired listing of the directory.  In
> that case a good way to access what you want is to sort the dired buffer
> by date.  I use Ido too, but I use bookmarks much more.
>
> BR,
> Robert Thorpe
>

I use icicles with recentf, it works very  nicely, as you might expect. I
also use icicles to navigate bookmarks (bookmarks+) which then gives us
best of all worlds.

See http://www.emacswiki.org/emacs/Icicles_-_Bookmark_Enhancements

I was a big ido fan, but converted to icicles mainly for superior tag
navigation.

Cheers

Will


  reply	other threads:[~2014-11-01 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 10:22 Moving from Ido to Icicles Marcin Borkowski
2014-11-01 14:48 ` Dale Snell
2014-11-01 21:07   ` Robert Thorpe
2014-11-01 23:35     ` Will O'Brien [this message]
2014-11-04  7:23       ` Drew Adams

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=CAKgE0sCOKPLx_ez8fY823wV0fTDJ6vM5J7aQoNQB0_49fg87wg@mail.gmail.com \
    --to=will.08rien@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rt@robertthorpeconsulting.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).