Re: [9fans] History

[rog@vitanuova.com]

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

some long commands don't deserve to be put into a function.  i'm
thinking of the usual only-useful-this-time one-shots like

for (i in `{tail -4000 odd | tr ' ' '\012' | sort | uniq -c | sort -rn | sed 's/ *[0-9]+ //'}) {
	if (test -f $home/dict/$i) {echo strange}
}

although it's probably never going to be used again, sometimes one
remembers "oh yes, i did something like that a while back" and it's
nice if it hasn't gone forever.

acme win is better than rio, where a reasonable amount of debug output
causes all previously typed commands in that window to be lost.

i'm sure there must be a better way.

  rog.


[-- Attachment #2: Type: message/rfc822, Size: 1540 bytes --]

To: cse.psu.edu!9fans
Subject: [9fans] History
Date: Thu, 9 Nov 2000 09:01:18 -0500
Message-ID: <20001109142326.3091D199F1@mail.cse.psu.edu>

You wouldn't feel the need for history so much if you
didn't type such long commands.  Try mk or make or
defining a function.  It's much less work to type
	mk
than
	gcc -Isomenonstandardplace -Dverylongoption -Wpleasedontcomplainaboutmyprogramiknowhatimdoing ilikethingstobeclearsoigivemyfileslongnames.c

-rob