unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: convert-standard-filename's doc
Date: Sat, 29 May 2004 16:24:06 +0200	[thread overview]
Message-ID: <7704-Sat29May2004162405+0300-eliz@gnu.org> (raw)
In-Reply-To: <86y8nbpjt8.fsf@rumba.de.uu.net> (message from Kai Grossjohann on Sat, 29 May 2004 13:13:55 +0200)

> From: Kai Grossjohann <kai@emptydomain.de>
> Date: Sat, 29 May 2004 13:13:55 +0200
> 
>     Convert a standard file's name to something suitable for the current OS.
>     This means to guarantee valid names and perhaps to canonicalize certain
>     patterns.
> 
>     On Windows and DOS, remove invalid characters.  On DOS, make sure to
>     obey the 8.3 format.  On Windows, turn Cygwin names into native
>     names, and also turn slashes into backslashes if the shell requires it.

This doc string is fine with me, except ``remove invalid characters''
is not quite true; ``replace'' is closer.  Also, I would add an
explicit reference to w32-shell-dos-semantics.  So:

    Convert a standard file's name to something suitable for the current OS.
    This means to guarantee valid names and perhaps to canonicalize certain
    patterns.

    On Windows and DOS, replace invalid characters.  On DOS, make sure to
    obey the 8.3 limitations.  On Windows, turn Cygwin names into native
    names, and also turn slashes into backslashes if the shell requires it
    (see `w32-shell-dos-semantics').

  reply	other threads:[~2004-05-29 14:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 14:05 convert-standard-filename's doc Juanma Barranquero
2004-05-27 18:21 ` Eli Zaretskii
2004-05-27 22:19   ` Stefan Monnier
2004-05-28  9:02     ` Eli Zaretskii
2004-05-28 16:19       ` Stefan Monnier
2004-05-29 11:40         ` Eli Zaretskii
2004-05-28  9:27     ` Juanma Barranquero
2004-05-28 13:51       ` Kai Grossjohann
2004-05-28 18:26         ` Juanma Barranquero
2004-05-29 11:13           ` Kai Grossjohann
2004-05-29 14:24             ` Eli Zaretskii [this message]
2004-05-29 14:47               ` Kai Grossjohann
2004-05-29 17:55             ` Juanma Barranquero
2004-05-30 21:53               ` {Spam?} " Stefan Monnier
2004-05-31  7:05               ` Eli Zaretskii
2004-05-31  7:39                 ` Juanma Barranquero
2004-05-29 12:08           ` Eli Zaretskii
2004-05-28 16:21       ` Stefan Monnier
2004-05-29  0:49         ` Juanma Barranquero
2004-05-29 17:02         ` Richard Stallman
2004-05-29 17:56           ` Juanma Barranquero
2004-05-29 11:18     ` Kai Grossjohann
2004-05-30 14:30       ` Richard Stallman
2004-05-28  7:28   ` Juanma Barranquero
2004-05-29 10:16     ` Eli Zaretskii
2004-05-28  5:22 ` Kai Grossjohann
2004-05-28  9:32   ` Juanma Barranquero

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=7704-Sat29May2004162405+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.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).