From: Richard Stallman <rms@gnu.org>
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: Undocumented hyperlinks in doc strings.
Date: Thu, 16 Oct 2003 10:06:58 -0400 [thread overview]
Message-ID: <E1AA8mI-0003mI-Hl@fencepost.gnu.org> (raw)
In-Reply-To: <200310150138.h9F1cWg10456@raven.dms.auburn.edu> (message from Luc Teirlinck on Tue, 14 Oct 2003 20:38:32 -0500 (CDT))
That could be mended by a slight change in the current standard
(which, to me, means: "as recommended in the Elisp manual") way of
commenting out code, which I proposed in an earlier message: follow
the semicolons by a single space if the line is meant to be a heading
line and by at least two spaces otherwise.
That convention, in itself, would not hurt anything. But if we wanted
to follow it all the time, what exactly would we make comment-region
do, for Lisp code? Would we make it insert two spaces always? Two
spaces, when given an arg of 3? And what would uncomment-region do?
If we make it try to remove two spaces (when there are two),
then it would uncomment all the existing commented-out code wrong.
I am not saying that these answer have to be perfect, but we need
to pick answers.
next prev parent reply other threads:[~2003-10-16 14:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 0:50 Undocumented hyperlinks in doc strings Luc Teirlinck
2003-10-09 21:16 ` Richard Stallman
2003-10-10 3:27 ` Luc Teirlinck
2003-10-10 14:14 ` Stefan Monnier
2003-10-10 15:31 ` Luc Teirlinck
2003-10-10 16:29 ` Luc Teirlinck
2003-10-10 17:23 ` Stefan Monnier
2003-10-10 18:21 ` Luc Teirlinck
2003-10-10 19:24 ` Stefan Monnier
2003-10-11 17:12 ` Richard Stallman
2003-10-14 21:03 ` Stefan Monnier
2003-10-15 1:38 ` Luc Teirlinck
2003-10-15 20:00 ` Richard Stallman
2003-10-15 23:52 ` Luc Teirlinck
2003-10-16 23:06 ` Richard Stallman
2003-10-16 14:06 ` Richard Stallman [this message]
2003-10-17 3:32 ` Luc Teirlinck
2003-10-17 13:47 ` Stefan Monnier
2003-10-18 23:06 ` Richard Stallman
2003-10-19 1:14 ` Luc Teirlinck
2003-10-20 1:48 ` Richard Stallman
2003-10-20 2:24 ` Luc Teirlinck
2003-10-20 14:44 ` Stefan Monnier
2003-10-20 15:22 ` Luc Teirlinck
2003-10-21 14:47 ` Richard Stallman
2003-10-11 5:36 ` Richard Stallman
2003-10-12 3:34 ` Luc Teirlinck
2003-10-13 5:03 ` Richard Stallman
2003-10-14 3:23 ` Luc Teirlinck
2003-10-17 20:46 ` Richard Stallman
2003-10-17 23:30 ` Luc Teirlinck
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=E1AA8mI-0003mI-Hl@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).