Hello Jorj,
\|/ Subject: orphaned descriptions
/|\ On Monday April 13 1998 at 00:15,
you wrote to Gerald Miller saying:
GM>> This is one of those apples versus oranges comparisons...
JS> Both will work. One uses the command explicitly designed for it, and
JS> one accomplishes it by the back door.
These are the kind of things that are not totally clear within the help file,
but I guess there is only so much you can put into an on-line help file...
JS> I think my comment was a remnant of thinking that you were trying to
JS> save DESCRIPT.ION, not save a description it it.
Most people worry about saving a file; I like to worry about saving a little
description because I dislike repetitive typing ,-))
GM>> when I did a DIR listing and then viewed the descript.ion file
GM>> afterwards, the filenames and descriptions were gone.
JS> Odd. I hadn't thought that DIR alone cleared orphans. Only deleting
JS> or moving seems to in some quick tests.
This could be because of my alias for one of the DIR commands -- uses some
switches and a pipe command...
GM>> Number one: Delete ALL the ANTI-VIR.DAT files on ALL drives, in ALL
GM>> directories and subdirectories (without updating the description for
GM>> this file in DESCRIPT.ION).
JS> Is the description the same everywhere?
Yes. It's just too much bother to "customize" the description for every
directory.
JS> Because if it is, it's probably easier to globally recreate it than
JS> preserve it.
GM>> How would one "read" the DESCRIPT.ION file and verify that
GM>> ANTI-VIR.DAT is described only once?
JS> Personally, I wouldn't. I'd just redescribe the file. That process
JS> would prune the DESCRIPT.ION file in the unlikely event there are
JS> duplicates.
I think this is the best possibility. I'll refer back to one of your
previous messages where you talked about an AVD variable...
JS> Or one could do
JS> ffind /a:h /v /t"*anti-vir.dat*" descript.ion
I took your above line, added a "/s" between the /v /t and ran it from the
root directory. I like this command and can think of a few other uses for
it. Pity that I've not used it sooner...
JS> That gets you a full list. You could redirect that to a file, and
JS> then grab the penultimate word on the last line of that file:
JS> %@word[-1,[%@line[$di,%@lines[$di]]]
JS> for the number of appearances
I haven't tried the above command because I'm not sure how it could be used.
Perhaps a small BTM example...
G'Day ... Gerald
--- GoldED/386 3.00.Beta2 UNREG
---------------
* Origin: 4DOS for one and 4DOS for all! (1:153/715.6)
|