unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Cc: emacs-pretest-bug@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: recentf-cleanup, file-readable-p & remote files
Date: Wed, 17 Sep 2003 04:10:49 +0200	[thread overview]
Message-ID: <m3znh4tb9y.fsf@defun.localdomain> (raw)
In-Reply-To: <14940442.1063698697392.JavaMail.www@wwinf0603> (David PONCE's message of "Tue, 16 Sep 2003 09:51:37 +0200 (CEST)")

David PONCE <david.ponce@wanadoo.fr> writes:

> IMO a better solution would be to allow to disable connection
> timeout when calling the `file-readable-p' remote handler (I don't
> know if this is feasible).  So when not connected, `file-readable-p'
> will immediately return nil, without waiting for a remote
> connection.

Ah, I think you misunderstood part of what I was trying to say --
which is that `file-readable-p' can be very slow when you *are*
connected (when I'm not connected it returns in a fraction of second,
so that's not a problem)

The reason is that that ange-ftp implements it rather inefficiently.
Instead of just listing the file in question it lists *all* files in
the directory.  That's a lot of data if the directory contains
thousands of files.  In the example from my previous post doing
`file-readable-p' is ~500 times slower than actually fetching the
file!

-- 
Cheers,
Jesper Harder

  parent reply	other threads:[~2003-09-17  2:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16  7:51 recentf-cleanup, file-readable-p & remote files David PONCE
2003-09-16  7:58 ` Miles Bader
2003-09-17 18:02   ` Richard Stallman
2003-09-17 20:12     ` Jesper Harder
2003-09-18 15:14       ` Richard Stallman
2003-09-17  2:10 ` Jesper Harder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-18  8:48 David PONCE
2003-09-19  1:45 ` Jesper Harder

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=m3znh4tb9y.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-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).