From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: convert-standard-filename's doc
Date: Sat, 29 May 2004 14:08:17 +0200 [thread overview]
Message-ID: <9743-Sat29May2004140817+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040528200923.5B69.LEKTU@mi.madritel.es> (message from Juanma Barranquero on Fri, 28 May 2004 20:26:12 +0200)
> Date: Fri, 28 May 2004 20:26:12 +0200
> From: Juanma Barranquero <lektu@mi.madritel.es>
>
> Doing what you suggest means a longish docstring with much non-useful
> info (non-useful for each system's users, I mean), and fixing all
> versions of the docstring each time one of the functions is changed or a
> new system added.
We could have a short version in the doc string and a longer one in
the manual.
In any case, I think Kai is right saying that the doc string should
give more emphasis to the fact that the function makes the file name
a valid one for the underlying platform.
next prev parent reply other threads:[~2004-05-29 12:08 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
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 [this message]
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=9743-Sat29May2004140817+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).