Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!oliveb!amdahl!amdcad!rpw3
From: rpw3@amdcad.AMD.COM (Rob Warnock)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  syntax of remote pathnames?
Message-ID: <25021@amdcad.AMD.COM>
Date: 29 Mar 89 05:18:36 GMT
References: <8903281410.AA04667@hogg.cc.uoregon.edu> <3728@phri.UUCP>
Reply-To: rpw3@amdcad.UUCP (Rob Warnock)
Organization: [Consultant] San Mateo, CA
Lines: 35

In article <3728@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
+---------------
| > one could even imagine a file system that allowed CR, LF, or CRLF
| > in a pathname.
| 	You mean like the Unix file system?  To wit:
| $ echo xxx* | od -c
| 0000000    x   x   x  \r  \n   y   y   y  \n
+---------------

I even had a use for one of these. When bouncing around a certain LAN I got
so tired of not remembering what a given host's way to clear the screen was
(some systems had a "clear" command, others not) that I put a shell script
in my ~/bin/ on each system to do that. Since my favorite terminal (at the
time) used a form-feed to clear the screen, that's what the name of the
program was: <^L> (the single character 0x0C). Worked fine! (On Unix...)

And a certain computer company whose terminals emitted the triplet <^A>x<CR>
(for various "x") taught its "office automation" users (sec'ys, etc.) to
make "friendly" shell scripts whose names were some function key, so users
could "customize" their terminals with single buttons that, for example,
read mail. To wit:

	% vi <F3>	# note no need to type RETURN after hitting <F3>
	...edit the Function-Key-3 script...
	% chmod a+x <F3>
	% <F3>
	...and the script named "<^A>c<CR>" runs...


Rob Warnock
Systems Architecture Consultant

UUCP:	  {amdcad,fortune,sun}!redwood!rpw3
DDD:	  (415)572-2607
USPS:	  627 26th Ave, San Mateo, CA  94403