🚀 go-pugleaf

In article <829701126snz@tsys.demon.co.uk>
           tomw@tsys.demon.co.uk "Tom Wheeley" writes:

> I know memory is tight for KA9Q, but would it be possible to introduce code
> for forming legal 8.3 filenames?
> 
> f.e. when getting a FAQ from rtfm.mit.edu, they are stored with the Subject:
> line as filename, which is often about 80 characters of case-sensitive and
> punctuation filled typo fodder.
> 
> What would be nice, would be to be able to type `mget faq??name*etc*' (with
> the expression matching solely the required filename), and have a file be got,
> albeit with a silly name.  At present, the chances of DOS finding a legal
> 8.3 name is as remote as DOS accepting a 255 char name :(
> 
> Perhaps a simpler solution would be to prompt for a new filename if DOS
> rejects the default one, or if the file exists locally?

This is another interesting problem. AFAIK, mget is implimented as a dir
on the relevant wildcard followed by a loop for all files in that list
where each iteration gets a file.  I would insert some additional logic
as follows:

In get, get the 1st 8 alphameric characters which precede the last
period in the Unix name and the 1st 3 alphameric characters which follow
that final period.  If that name is not already in use, use it and
report what has been done. Otherwise, prompt for an alternative.

For mget, If repeated use of the name generation logic in get caused a
problem, I would have a directory tree created to hold the files, report
the activity and let the user sort the problem at his/her convenience.

N.B.  This is not so interesting to me that I am prepared to put the
time into doing it.  ka9q is ENORMOUS and my cage is more rattled by
other problems. See thread on Snews EXPIRE.
-- 
walter briscoe