Here are some observations I've made after attempting to use rcp.el
for the first time. Needless to say, they aren't very
"sophisticated", but since I see it with fresh eyes, this may be
informative.
--
After installing rcp.el
Dale R Worley <[EMAIL PROTECTED]> 4/18/00 1:10:57 PM >>>
> Observation: One of the greatest virtues of ange-ftp.el is that it
> "just works". After installing it, one can use it productively
> without further changes. This is a tremendous aid to people adopting
> it. It would be very useful if rcp
Let me try to flesh out my remarks.
First off, most of this stuff is "usability engineering". It's not
comments on the correctness of the code per se, but recognizing that
it takes quite a bit of experience, design, and tinkering to make
something *easy to use*. This is important, because ease
[EMAIL PROTECTED] (Kai Großjohann) writes:
> Sadly, the life of rcp.el is not so simple.
I think I might have been overly protective and defensive when
replying to your message, Dale. Now that I've thought about it, `hard
to implement' is a pretty lame excuse. Please do not refrain from
kickin
"Tom Roche" <[EMAIL PROTECTED]> writes:
> [...] It'd be nice if the user could specify (perhaps even by
> server) a sequence of preferred transports. E.g. for ssh.ncsu.edu I
> want only to transfer via scp; for ftp.ncs.ncsu.edu I want to
> transfer via scp but will transfer via ftp if that fails;
Dale R Worley <[EMAIL PROTECTED]> writes:
> The documentation for the entries in rcp-methods seems to be a bit
> weak. It does specify what you're specifying, but it doesn't really
> tell what will be done once the programs are run.
Thanks for this report. I have written up the following secti
Martin Pool <[EMAIL PROTECTED]> writes:
> I would be *so* happy if there was a simpler version that worked for
> me. The functionality like remote vc is great, but I haven't been able to
> use it for ages.
I think that it is possible to get it to work for you, there is just
(well) some debuggin
From: [EMAIL PROTECTED] (Kai=?iso-8859-1?q?_Gro=DFjohann?=)
Let's talk about the question part. rcp.el could do the following
things:
(1) Have a list of regexp/action pairs. Each time that output is
received from the remote end, look for one of a number of regular
exp
On 18 Apr 2000, Kai Großjohann wrote:
> [EMAIL PROTECTED] (Kai Großjohann) writes:
>
> > Sadly, the life of rcp.el is not so simple.
>
> I think I might have been overly protective and defensive when
> replying to your message, Dale. Now that I've thought about it, `hard
> to implement' is a p
Dale R Worley <[EMAIL PROTECTED]> writes:
> Here are some observations I've made after attempting to use rcp.el
> for the first time. Needless to say, they aren't very
> "sophisticated", but since I see it with fresh eyes, this may be
> informative.
Thanks a lot for your observations, I really
> "Kai" == Kai Großjohann <[EMAIL PROTECTED]> writes:
> Or should I put code in it that barfs for old Emacsen?
I've seen too many times such code barf later on for newer Emacsen.
Furthermore, maybe someone have Emacs-19 with enough add-on packages
that rcp.el indeed works for him.
Just docum
Dale R Worley <[EMAIL PROTECTED]> writes:
> Kai Grossjohann writes:
>
> > Let's talk about the question part. rcp.el could do the following
> > things:
> >
> > (1) Have a list of regexp/action pairs. Each time that output is
> > received from the remote end, look for one of a number of regu
Dale R Worley <[EMAIL PROTECTED]> writes:
> Let me try to flesh out my remarks.
Thanks a lot. It is obvious that you know very well what you're
talking about, and I only wish that I can participate from this a bit,
so as to improve rcp.el.
> First off, most of this stuff is "usability engineer
From: "Stefan Monnier" <[EMAIL PROTECTED]>
> Or should I put code in it that barfs for old Emacsen?
I've seen too many times such code barf later on for newer Emacsen.
Furthermore, maybe someone have Emacs-19 with enough add-on packages
that rcp.el indeed works for him.
Just d
Dale R Worley <[EMAIL PROTECTED]> writes:
> Well, you should be able to depend on (emacs-version) over the long
> haul. But definitely, you should be able to reduce it to a small
> experssion that can be clipped out if the user has an Emacs-19 that he
> wants to test it with.
To reduce what to
> "Dale" == Dale R Worley <[EMAIL PROTECTED]> writes:
> To reduce the test that the current Emacs is version 20 or later to a
> small expression.
The test is there already, really:
(defgroup rcp nil
"Edit remote files with a combination of rsh and rcp or similar programs."
:g
From: [EMAIL PROTECTED] (Kai =?iso-8859-1?q?Gro=DFjohann?=)
> Well, you should be able to depend on (emacs-version) over the long
> haul. But definitely, you should be able to reduce it to a small
> experssion that can be clipped out if the user has an Emacs-19 that he
> wants to
"Stefan Monnier" <[EMAIL PROTECTED]> writes:
> The test is there already, really:
He, he. Cool. So people wanting to try this on Emacs 19 need to get
the unbundled Customize, or they define dummy functions.
kai
--
Beware of flying birch trees.
From: "Stefan Monnier" <[EMAIL PROTECTED]>
> To reduce the test that the current Emacs is version 20 or later to a
> small expression.
The test is there already, really: [...]
`defgroup' is not defined in Emacs-19.
But that's hardly a user-friendly way to report the problem to
Dale R Worley <[EMAIL PROTECTED]> writes:
> But that's hardly a user-friendly way to report the problem to the
> naive user.
I have now documented it in the beginning of rcp.el.
kai
--
Beware of flying birch trees.
Kai Großjohann writes:
>>> rcp.el could do the following things:
>>> (1) Have a list of regexp/action pairs. Each time that output is
>>> received from the remote end, look for one of a number of
>>> regular expressions. Depending on the regexp that matched,
>>> take some action.
>>>
Now that Kai has added connection chaining and ability to use su, the
benefit of rcp.el is increased by an order of magnitude.
>From a single Emacs session on the localhost, I can edit files owned
by other users (such as root) on my local box or on boxes behind
firewalls across the 'net. The po
22 matches
Mail list logo
