unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Rustom Mody" <rustompmody@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: caching recent files
Date: Tue, 19 Aug 2008 12:31:31 +0530	[thread overview]
Message-ID: <f46c52560808190001w61cefab5q6c944c49affe07b4@mail.gmail.com> (raw)
In-Reply-To: <000001c90149$d557c7f0$0200a8c0@us.oracle.com>

Thanks
Yeah Icicles is on my list of things to check out.  I figured that it
would have something related to this but I could not find it.
I then tried filesets and the fileset-cache became some 4M (!!) so I
guess I will try out icicles.
What should I start by reading?

On Mon, Aug 18, 2008 at 9:18 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> I have been studying how to maintain recent files and am confused by
>> the available functionality.
>>
>> recentf keeps recent files but not directories
>> file cache is not persistent -- so not clear what its use is.
>>
>> So what is the recommended way of maintaining a readily available list
>> of files and dirs? I guess there is filesets but I find that very
>> hard to understand :-)
>
> Do you want (1) just recent files, or do you want to create and save (2) an
> arbitrary set of files and directories that you can return to later?
>
> 1. For recent files, I use recentf. I use `icicle-recent-file', actually, which
> lets you complete against parts of the file names.
>
> 2. You can use Icicles to create and save named sets of files and dirs for later
> use. See http://www.emacswiki.org/cgi-bin/wiki/Icicles_-_Persistent_Completions.
>
>




  reply	other threads:[~2008-08-19  7:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 14:07 caching recent files Rustom Mody
2008-08-18 15:48 ` Drew Adams
2008-08-19  7:01   ` Rustom Mody [this message]
2008-08-19 15:26     ` Drew Adams
2008-08-18 16:06 ` Nikolaj Schumacher
2008-08-19  6:39   ` Rustom Mody

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=f46c52560808190001w61cefab5q6c944c49affe07b4@mail.gmail.com \
    --to=rustompmody@gmail.com \
    --cc=drew.adams@oracle.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).