Kai Gro�johann wrote:
[...]
> not mention the remote directory.  What happens if you try
> /r@scp:juliano@capefear:~/.emacs instead?  Note the ``~/'' part.

yes, this seems to work.  now I get

    (setq f "/r@scp:juliano@capefear:~/.emacs") 
    "/r@scp:juliano@capefear:/.emacs"

    (file-name-directory f)
    "/r@scp:juliano@capefear:~/"

    (file-name-nondirectory f)
    ".emacs"

only, ssh still segfaults.  I think it's because I didn't run
ssh-agent?  Kai suggested that I try slm. 
"/r@slm:juliano@capefear:~/.emacs TAB", it asks me for my password

  slogin -l juliano capefear -- password:

I type it in, then get this error

  Process *rcp/slm juliano@capefear* exited abnormally with code 128

When I type "slogin -l juliano capefear" at my bash prompt (on my PC), I
get this for the prompt

  juliano@capefear's password:

Unless this is a bug that was fixed after 10/7 (I have version 1.555),
I'm stuck.  But I'll try upgrading, anyway.  Here's the backtrace:

Signaling: (error "Couldn't find password prompt.  See buffer `*rcp/slm
juliano@capefear*' for details")
  signal(error ("Couldn't find password prompt.  See buffer `*rcp/slm
juliano@capefear*' for details"))
  error("Couldn't find password prompt.  See buffer `%s' for details"
"*rcp/slm juliano@capefear*")
  rcp-open-connection-rlogin("slm" "juliano" "capefear")
  rcp-maybe-open-connection("slm" "juliano" "capefear")
  rcp-send-command("slm" "juliano" "capefear" "cd ~; pwd")
  rcp-handle-expand-file-name("/r@slm:juliano@capefear:~/" "c:/Program
Files/emacs-20.4/site-lisp/")
  apply(rcp-handle-expand-file-name ("/r@slm:juliano@capefear:~/"
"c:/Program Files/emacs-20.4/site-lisp/"))
  rcp-file-name-handler(expand-file-name "/r@slm:juliano@capefear:~/"
"c:/Program Files/emacs-20.4/site-lisp/")
  read-file-name-internal("/r@slm:juliano@capefear:~/.emacs" "c:/Program
Files/emacs-20.4/site-lisp/" nil)
  minibuffer-complete()
  call-interactively(minibuffer-complete)
  call-interactively(find-file)


(FWIW, I can't use ssh-agent yet because I still haven't updated my
cygwin dll to a more recent version.  If anyone else it trying to get
ssh to work on their windows pc, ssh-agent reportedly works if you
update cygwin.dll to a recent snapshot or to the 1.0 release.  Under the
B20.1 release, everything else does work, AFAIK.)

> I just tested this on my FreeBSD Emacs 20.4 (emacs -q -no-site-file,
> not loading rcp.el) and it seemed to do something sensible.  If that
> works with NT Emacs, too, then I think it is reasonable to require the
> users to explicitly specify the remote directory.
> 
> What do you think?

sounds fair to me.  as long as it's documented.

thanks,

-jeff

Reply via email to