On Apr 11,  9:06pm, Gavin Scott wrote:
...
> Hmmm.  Here's another alternative.  Maybe some combination that highlights
> the fact that it is a header line, such as:
>
> :listf @,10
> Account=  SYS         Group=  OTHER
> Name----* Code- Size---  Type EOF--------- Limit-------
...
I like this.  One reason I didn't propose MiXed case headers is that I
was hoping to share LISTF,1 and ,2 code better.  Bad reason since user
testing has shown that readability is improved with mixed case.
...
> What about inserting another space delimited
> column between Name and Code that would be between 2 and 5 characters wide...
> Maybe something like
> a comination of the letters RWEX indicaing open for Read, open for Write,
> Open Exclusively, being eXecuted, etc.  Just a thought.

R,W and E is available to LISTF,10 or ,11.  A new "Acc"ess col
could contain the following values:
   R   - read-only
   W   - write-only
   RW  - read/write
   ER  - read, exclusive
   EW  - write, exclusive
   ERW - read/write, exclusive
(shared access is implied by the absence of 'E')

:listf @,11
Account=  SYS         Group=  OTHER
Name---- Acc Code- Size--  Type EOF--------- Limit------- K Bytes---
LARGE                  80  FA            500   1234567890         40
LARGE1                 80  FA    12345678902  12345678902  987654313
L2345678 ERW AAAAA 999998  FBxx 999999999999 999999999999 9999999999

In this version I dropped the 'B' suffix for record size since bytes would
always be assumed.

These changes probably make the new formats more useful, but at the cost
of making the quick'n'dirty 2am change to an app that bombed on a large
file all the more tedious.

> > :listfile ./@,20 (or "Ldisc")
>                 ^^Don't you mean 11? :-)

ooops.  Yup.  All the new format examples should be ,10 or ,11.

Jeff

--