From: Lars Hansen <larsh@math.ku.dk>
Cc: tramp-devel@nongnu.org, kai@emptydomain.de,
monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: ls-lisp and remote files
Date: Fri, 14 Nov 2003 11:36:19 +0100 [thread overview]
Message-ID: <3FB4B023.2010708@math.ku.dk> (raw)
In-Reply-To: <E1AK7OK-0001Xz-IQ@fencepost.gnu.org>
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.
next prev parent reply other threads:[~2003-11-14 10:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 20:06 ls-lisp and remote files Lars Hansen
2003-10-30 20:25 ` Stefan Monnier
2003-11-05 21:39 ` Kai Grossjohann
2003-11-06 13:37 ` Stefan Monnier
2003-11-06 14:25 ` Lars Hansen
2003-11-08 2:16 ` Richard Stallman
2003-11-09 21:29 ` Lars Hansen
2003-11-10 21:57 ` Richard Stallman
2003-11-11 7:03 ` Lars Hansen
2003-11-12 2:29 ` Richard Stallman
2003-11-12 10:41 ` Lars Hansen
2003-11-13 2:39 ` Richard Stallman
2003-11-13 17:21 ` Kevin Rodgers
2003-11-13 18:05 ` Andreas Schwab
2003-11-13 18:48 ` David Kastrup
2003-11-14 20:09 ` Richard Stallman
2003-11-14 10:36 ` Lars Hansen [this message]
2003-11-12 22:12 ` Kai Grossjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FB4B023.2010708@math.ku.dk \
--to=larsh@math.ku.dk \
--cc=emacs-devel@gnu.org \
--cc=kai@emptydomain.de \
--cc=monnier@IRO.UMontreal.CA \
--cc=tramp-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).