unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Hadsell <ahadsell@mtdiablo.com>
Cc: gnu-emacs-bug@gnu.org
Subject: Re: Inconvenience with TRAMP and recentf
Date: Mon, 02 Jul 2007 06:15:59 +0300	[thread overview]
Message-ID: <usl87lcls.fsf@gnu.org> (raw)
In-Reply-To: <ulkdz93f4.fsf@mtdiablo.com> (message from Alan Hadsell on Sun, 01 Jul 2007 18:15:11 -0400)

> From: Alan Hadsell <ahadsell@mtdiablo.com>
> Date: Sun, 01 Jul 2007 18:15:11 -0400
> Cc: 
> 
> There are several workarounds for this problem: I can reconfigure
> recentf-auto-cleanup to 'never, or exclude TRAMP files from the
> recentf list; neither of these approaches is really appealing.  I'm
> sure there are other ways, too.
> 
> I was thinking to add a boolean recentf-cleanup-local-files-only,
> which would allow us to avoid trying to do cleanup for TRAMP files.

Why does it make sense not to cleanup only remote files?

> Before I go away to hack on that solution, does anyone have a better
> idea?

How about setting recentf-auto-cleanup to a number, which will cause
the cleanup to happen when Emacs is idle for that many seconds?  That
should avoid the startup delay without having the adverse effects of
keeping stale files on the list.

  reply	other threads:[~2007-07-02  3:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 22:15 Inconvenience with TRAMP and recentf Alan Hadsell
2007-07-02  3:15 ` Eli Zaretskii [this message]
2007-07-02  4:51 ` Michael Albinus
     [not found] ` <mailman.2935.1183346169.32220.bug-gnu-emacs@gnu.org>
2007-07-02 15:08   ` Alan Hadsell
     [not found] ` <mailman.2937.1183364176.32220.bug-gnu-emacs@gnu.org>
2007-07-02 15:31   ` Alan Hadsell
2007-07-02 19:37     ` Michael Albinus
     [not found]     ` <mailman.2973.1183405011.32220.bug-gnu-emacs@gnu.org>
2007-07-02 21:31       ` Alan Hadsell

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=usl87lcls.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=ahadsell@mtdiablo.com \
    --cc=gnu-emacs-bug@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).