Re: ls-lisp and remote files

[Lars Hansen]

Richard Stallman wrote:

> The option should be designed so that there is a non-nil value meaning
> "numbers" and another non-nil value meaning "strings", so that we can
> someday change the meaning of nil.
>  
I like that idea. How about this:

We introduce a parameter ID-FORMAT with the following meaning:
If ID-FORMAT is numeric or nil, UID and GID are returned as integers, 
otherwise as strings.

Over time we can change all calls so they include ID-FORMAT with a value 
of 0 or t, and we can try to avoid using 0. Once the lisp source has no 
calls with ID-FORMAT left out, we can change the meaning of nil such 
that UID and GID are returned as strings in that case. Then we can 
remove the parameter from the calls where it has value t, and if the 
parameter then is unused, we may even remove it from the definition.

These plans should be written in the lisp manual and the TODO file, I think.