Jeffrey uses NT and has a couple of problems with rcp.  I wonder
why.  Apparently, everything after the first colon is chopped off
before rcp ever sees the filename.  Hm.  But this doesn't happen with
ange-ftp, so what's wrong?

kai
-- 
Life is hard and then you die.



Topics:
   rcp.el questions
   Re: rcp.el questions
   Re: rcp.el questions
   Re: rcp.el questions


----------------------------------------------------------------------

Date: Fri, 08 Oct 1999 14:57:00 -0400
From: Jeffrey Juliano <[EMAIL PROTECTED]>
To: Kai =?iso-8859-1?Q?Gro=DFjohann?= <[EMAIL PROTECTED]>
Subject: rcp.el questions
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I'm having trouble getting rcp.el to work.  I'd appreciate if you can
help me to troubleshoot this.  Feel free to request that tests to
perform on my particular platform configuration.


I downloaded rcp.el, RCS version 1.155; placed it in site-lisp, and
byte-compiled it.

Next, I run emacs and do "M-x load-library rcp".  (this is equivalent to
eval'ing (require 'rcp) in a lisp buffer, right?)

- ----------

Next, I try

  C-x C-f //r@scp:juliano@capefear:.em TAB

and get the following message

  Not an rcp file name: /r@scp:

If I instead try

  C-x C-f //r@scp:capefear:.em TAB

I get the same error.  However, if I eval

  (setq rcp-default-method "scp")

then do

  C-x C-f r:juliano@capefear:.emacs RET

it creates a new file called "juliano@capefear:.em".


- -------------

 * I'm running on winNT, precompiled 20.4.1 binary.
 * I don't have an rsh or rcp program.
 * Instead, I use ssh/scp compiled under cygwin.
 * I can do "ssh capefear" from a cygwin/bash shell, but it doesn't work
right from a dos shell. 
 * I have shell-file-name set to my bash shell.
   * I have no problem doing local compiles, grep, grep-find, etc from
emacs using the bash shell.
 * ssh-agent does not work


is ssh-agent necessary for rcp.el to work?

I'm still trying to set things up so I can run emacs on my local PC, and
do remote compiles on a Unix server.

I'm willing to help you debug this.  (but I'm far from a lisp expert)  I
have no idea where to start looking.  Any suggestions?

thanks,

- jeff

------------------------------

Date: 10 Oct 1999 01:16:23 +0200
From: [EMAIL PROTECTED] (Kai =?iso-8859-1?q?Gro=DFjohann?=)
To: Jeffrey Juliano <[EMAIL PROTECTED]>
Subject: Re: rcp.el questions
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii

Jeffrey Juliano <[EMAIL PROTECTED]> writes:

> I downloaded rcp.el, RCS version 1.155; placed it in site-lisp, and
> byte-compiled it.

Good.

> Next, I run emacs and do "M-x load-library rcp".  (this is equivalent to
> eval'ing (require 'rcp) in a lisp buffer, right?)

More or less.  `require' doesn't load the file if it is already
loaded, `load-library' loads it anyway.

> Next, I try
> 
>   C-x C-f //r@scp:juliano@capefear:.em TAB

Try /r instead of //r.

> and get the following message
> 
>   Not an rcp file name: /r@scp:

This is a result of the above problem.

>  * ssh-agent does not work
> is ssh-agent necessary for rcp.el to work?

No, ssh-agent is not necessary for rcp.el to work.  There are a number
of different ways to connect the remote host.  Have a look at the
variable rcp-methods.  The ones which use rcp-open-connection-rsh
require you to be able to log in without having to enter a password;
i.e. not the ones you want.  The ones which use
rcp-open-connection-rlogin require you to enter a password, so these
are the ones you want.  You can choose slm which uses mimencode (for
base64 encoding) or slu which uses uuencode/uudecode.  If you can
install mimencode on the remote host, please use that, base64 encoding
and decoding is built into Emacs and thus faster.

kai
- - 
Life is hard and then you die.

------------------------------

Date: Sat, 09 Oct 1999 20:55:51 -0400
From: Jeffrey Juliano <[EMAIL PROTECTED]>
To: Kai =?iso-8859-1?Q?Gro=DFjohann?= <[EMAIL PROTECTED]>
Subject: Re: rcp.el questions
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit



Kai Gro�johann wrote:
> 
> Jeffrey Juliano <[EMAIL PROTECTED]> writes:
> 
> > I downloaded rcp.el, RCS version 1.155; placed it in site-lisp, and
> > byte-compiled it.
> 
> Good.
> 
> > Next, I run emacs and do "M-x load-library rcp".  (this is equivalent to
> > eval'ing (require 'rcp) in a lisp buffer, right?)
> 
> More or less.  `require' doesn't load the file if it is already
> loaded, `load-library' loads it anyway.
> 
> > Next, I try
> >
> >   C-x C-f //r@scp:juliano@capefear:.em TAB
> 
> Try /r instead of //r.
> 
> > and get the following message
> >
> >   Not an rcp file name: /r@scp:
> 
> This is a result of the above problem.

nope.  I tried it without the extra slash.  doesn't work.  here's
another stack trace


Signaling: (error "Not an rcp file name: /r@slm:")
  signal(error ("Not an rcp file name: /r@slm:"))
  error("Not an rcp file name: %s" "/r@slm:")
  rcp-dissect-file-name("/r@slm:")
  rcp-handle-expand-file-name("/r@slm:" "c:/Program
Files/emacs-20.4/site-lisp/")
  apply(rcp-handle-expand-file-name ("/r@slm:" "c:/Program
Files/emacs-20.4/site-lisp/"))
  rcp-file-name-handler(expand-file-name "/r@slm:" "c:/Program
Files/emacs-20.4/site-lisp/")
  read-file-name-internal("/r@slm:[EMAIL PROTECTED]:.emacs"
"c:/Program Files/emacs-20.4/site-lisp/" nil)
  minibuffer-complete()
  call-interactively(minibuffer-complete)
  call-interactively(find-file)

looks like read-file-name-internal stripped too much???  Has anyone else
gotten it to work on winNT?  Does rcp-file-name-handler get passed the
entire filename on other platforms?  If this is the problem, how does
ange-ftp handle it?

I remember seeing something on the cygwin mailing list that in winNT
(and upcomming win2000? -- it's an issue with NTFS) that you can put an
optional colon and stream identifier on a filename.  Files in NTFS can
have more than one stream attached to them; an optional color followed
by an id is how you select a non-default stream.


> >  * ssh-agent does not work
> > is ssh-agent necessary for rcp.el to work?
> 
> No, ssh-agent is not necessary for rcp.el to work.  There are a number
> of different ways to connect the remote host.  Have a look at the
> variable rcp-methods.  The ones which use rcp-open-connection-rsh

I see.  makes sense.

thanks,

- jeff

------------------------------

Date: 10 Oct 1999 03:16:49 +0200
From: [EMAIL PROTECTED] (Kai =?iso-8859-1?q?Gro=DFjohann?=)
To: Jeffrey Juliano <[EMAIL PROTECTED]>
Subject: Re: rcp.el questions
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii

Jeffrey Juliano <[EMAIL PROTECTED]> writes:

>   rcp-file-name-handler(expand-file-name "/r@slm:" "c:/Program
> Files/emacs-20.4/site-lisp/")
>   read-file-name-internal("/r@slm:[EMAIL PROTECTED]:.emacs"
> "c:/Program Files/emacs-20.4/site-lisp/" nil)
>   minibuffer-complete()
>   call-interactively(minibuffer-complete)
>   call-interactively(find-file)
> 
> looks like read-file-name-internal stripped too much???  Has anyone else
> gotten it to work on winNT?  Does rcp-file-name-handler get passed the
> entire filename on other platforms?  If this is the problem, how does
> ange-ftp handle it?

Yes, you got it.  That seems to be the problem.  Normally, the entire
file name is passed to the file name handler.  I don't know why it
strips the part after the first colon.  Hm.

Btw, would you like to be on the rcp.el mailing list?  You could then
post your problem to the list.

It's 3am here, I'm going to go to bed, now.  See you tomorrow...

kai
- - 
Life is hard and then you die.

------------------------------

End of forward11318yaf Digest
*****************************


Reply via email to