unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: file-remote-p and its arguments
Date: Thu, 31 Jan 2008 09:49:09 -0500	[thread overview]
Message-ID: <jwvodb2oxxp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <nq7ihqwcsm.fsf@alcatel-lucent.de> (Michael Albinus's message of "Thu, 31 Jan 2008 10:43:21 +0100")

>> From what I can tell, the `connected' argument is *never* used.
> `recentf-keep-default-predicate'.

Indeed, thanks, I missed it.

> The reasoning is in
> <http://lists.gnu.org/archive/html/emacs-devel/2007-07/msg00416.html>

I see.  It does make sense :-(

>> And I have found only one use of the `identification' argument, if
>> grep.el where it seems not to be necessary: grep.el passes `host' for
>> that argument in order to build a map from hosts to default grep
>> commands and arguments, on the assumption that all users on a host will
>> have the same grep commands in their PATH.  I think this "optimization"
>> in grep.el (where they determine the grep defaults once per host instead
>> of once per remote access method (typically a triplet of
>> protocol/user/host)) is of no importance and is even not 100% reliable.

> It's less than an "optimization", it is just a kludge to let grep
> work also on remote hosts. The decision might be to either complete
> the implementation, or to throw away this feature.

This one I do not understand: using (file-remote-p file) for this
purpose would work just as well as (file-remote-p file 'host),
wouldn't it?


        Stefan




  reply	other threads:[~2008-01-31 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 21:26 file-remote-p and its arguments Stefan Monnier
2008-01-31  9:43 ` Michael Albinus
2008-01-31 14:49   ` Stefan Monnier [this message]
2008-01-31 15:49     ` Michael Albinus

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=jwvodb2oxxp.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).