unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
Cc: tramp-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: CORRECT VERSION:  tramp (2.0.51); tramp and file-name-all-completions
Date: Tue, 18 Oct 2005 10:47:00 +0200	[thread overview]
Message-ID: <nqirvvky9n.fsf@alcatel.de> (raw)
In-Reply-To: <m3ek6jeoce.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Tue, 18 Oct 2005 01:05:37 +0200")

storm@cua.dk (Kim F. Storm) writes:

>>> I used it in ido, and it seems to work:
>>>
>>> 	       ;; work around bug in ange-ftp.
>>> 	       ;; /ftp:user@host: => nil
>>> 	       ;; /ftp:user@host:./ => ok
>>> 	       (and
>>> 	        (not (string= "/ftp:" dir))
>>> 		(or
>>> 		 (string-match "\\`/ftp:.*:\\'" dir)
>>> 		 (and (string= tramp-default-method "ftp")
>>> 		      (string-match "\\`/[^/:]+:\\'" dir)))
>>> 		(file-name-all-completions "" (concat dir "./"))))))
>>
>> This works for Tramp 2.0. It will work for Tramp 2.1 too, but there
>> are also other means to derive a default methold. For the time being
>> you might use a comment for this.
>
> What code will I need to be 2.1 compatible?

Tramp uses internally `tramp-ftp-file-name-p' for ange-ftp and
`tramp-efs-file-name-p' for efs. Both functions expect a proper Tramp
file name syntax; you should check it before. Something like this:

;; work around bug in ange-ftp.
;; /ftp:user@host: => nil
;; /ftp:user@host:./ => ok
(and
 (tramp-tramp-file-p dir)
 (fboundp 'tramp-ftp-file-name-p dir)
 (funcall 'tramp-ftp-file-name-p dir)
 (string-match ":\\'" dir)
 (file-name-all-completions "" (concat dir "./")))

This should work for both Tramp 2.0 and 2.1; there are no plans to
change the interface.

>>> (file-directory-p "/telnet:kfs@")
>>>  or
>>> (file-directory-p "/telnet:kfs@:")
>>>
>>> tramp signals "Login failure" in both cases.  
>>
>> I know. This problem has eaten most of the time yesterday. In fact I
>> don't know a safe decision whether a file name shall be completed only
>> or "applied". Therefore I've introduced a new variable
>> tramp-completion-mode, which is set in
>> file-name-all-completions. Sensible Tramp file name functions, which
>> need to behave depending on the mode, check this variable (beside
>> other checks). So you might use it as well (untested, I'm @work):
>>
>> (let ((tramp-completion-mode t))
>>   (file-directory-p "/telnet:kfs@"))
>
> This still cause the "Login Failed" error...
>
> In any case, I don't quite understand how to use this.  How can ido
> know whether it makes sense to set tramp-completion-mode or not?

It cannot, because my proposal was nonsense.

The problem is that `file-directory-p' can give only an answer when it
accesses the remote host. If it is urged to just reply nil under
special circumstances, it is not worth to be called.

When you're doing file name completion, the file name is not complete,
and calling `file-directory-p' would try to access a host which does
not exist.

What we could do is to introduce an option saying "access this host
only if there is already a connection". This would avoid the "Login
Failed" error you've mentioned.

The question is what `file-directory-p' should return in case there
isn't a connection yet: nil, or a dont-know value as Richard did
suggest?

Best regards, Michael.

      reply	other threads:[~2005-10-18  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 22:04 CORRECT VERSION: tramp (2.0.51); tramp and file-name-all-completions Kim F. Storm
2005-10-17  4:49 ` Michael Albinus
2005-10-17 13:58   ` Kim F. Storm
2005-10-17 15:14     ` Michael Albinus
2005-10-17 17:46       ` Stefan Monnier
2005-10-18  8:51         ` Michael Albinus
2005-10-17 23:05       ` Kim F. Storm
2005-10-18  8:47         ` Michael Albinus [this message]

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=nqirvvky9n.fsf@alcatel.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=tramp-devel@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).