🚀 go-pugleaf

----
In article <8806021054.AA07856@lasso.laas.fr> ralph@lasso.UUCP (Ralph P. Sobek) writes:
->
->	mv can destroy files!!!!  without any message whatsoever.
->
->I found this problem when I was moving files from my hard disk to a
->full floppy disk.  After the move, the floppy had zero space left and *all*
->the files were deleted from the hard disk.  The problem is that not all the
->files made it to the floppy!!  SO BEWARE!!!
->

this is definitely a bug but...(and thanx for pointing it out!)

i don't know about you, but if i'm going to backup something to floppy and
then delete it (essentially mv) i ALWAYS cp, confirm that the copy worked with
(at a minimum) ls -l or (more thoroghly) cmp or diff (if really critical) and
only then do i rm the files, on any system, from a pc on up to a cray. it's
just not worth the headache if something should go wrong. in fact for very
important stuff, make 2 copies (i know, i'm just too paranoid...).

do you know if 1.03 has pipes? this is one essential feature lacking in an
otherwise great program (i played with MWC msh v1.x and immediately decide
gulam was infinitely better..except for pipes in which case i could just
start msh under gulam for the one command and exit but this is painful).

even being able to do this would be nice:

	alias pipe " > pipetmp0.000 ; \!2-$ <pipetmp0.000 ; rm pipetmp0.000"

then (say)
	
	history pipe grep ls

but this does not work (alas). i should see if this works under BSD csh...

-bill