"Edward J. Sabol" wrote:
Excerpts from [lists.emacs.rcp]: (07-Oct-99) Re: uuencode syntax? by Stefan Monnier
I'd say: kill that ugly uu(en|de)code beast and only support base64.
I agree. I was never a fan of adding uu*coding or base64 as transfer methods
to rcp.e
"K" == Kai Großjohann [EMAIL PROTECTED] writes:
K In the worst case, we would need four different methods: Linux
K style on both local and remote, BSD style on both, and two
K methods for Linux style on one side and BSD style on the other.
K Whee... Sounds really bad.
The idea
Edward J. Sabol [EMAIL PROTECTED] writes:
Excerpts from mail: (08-Oct-99) Re: uuencode syntax? by Kai
=?iso-8859-1?q?Gro=DFjohann?=
Any ideas for a uuencode replacement with awk and od?
No, but I think it's fairly simple to write one in Perl.
Yes, but perl doesn't come standard with most
--- David Barr [EMAIL PROTECTED] wrote:
Although I still have problems, because on some machines, my home
directory is remotely mounted from one server to machines of multiple
architectures. I could have multiple bin directories under my home
directory. I would usually handle this by
Edward J. Sabol [EMAIL PROTECTED] writes:
[...] (To be honest, I feel that's too many. I'm nostalgic for the
old days when rcp.el only supported rcp and scp.) [...]
Yes, yes, you're right. I wish I had a dwim command which just worked
:-( Or else, maybe a way to try out different
David Barr [EMAIL PROTECTED] writes:
[...] And even if I install it myself, I can't get it to work with
rcp.el because of the PATH issue which I described earlier. [...]
*blank look*
Que?
What PATH issue? Doesn't it work to add directories to
rcp-remote-path? rcp.el should add them to
[[ Mailed copy of news article posted to lists.emacs.rcp ]]
"Kai" == Kai Großjohann [EMAIL PROTECTED] writes:
Hm. That's bad. This means that it becomes rather more difficult to
use it. On the one hand, the syntax is the same for all uuencode
flavors, but on the other hand I have to
On Thu, Oct 07, 1999 at 05:17:10PM +0200, Kai Großjohann wrote:
Can you all do "uudecode --version 2/dev/null ; echo $?" and tell me
what you see?
On Solaris 2.6, I get exit status 2, and I have to use the "-p" thing.
On Linux, I get a line saying GNU sharutils and exit status 0, and I
Kai Großjohann wrote:
It seems that there are at least two versions of uuencode and uudecode
floating around, which have incompatible invocation syntax.
Encoding on Linux: uuencode foo FILE
Decoding on Linux: uudecode -o - FILE
Encoding on FreeBSD:uuencode FILE
It seems that there are at least two versions of uuencode and uudecode
floating around, which have incompatible invocation syntax.
Encoding on Linux: uuencode foo FILE
Decoding on Linux: uudecode -o - FILE
Encoding on FreeBSD:uuencode FILE
Decoding on FreeBSD:uudecode -p
10 matches
Mail list logo
