From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Undocumented hyperlinks in doc strings. Date: Thu, 16 Oct 2003 10:06:58 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200310090050.h990oIa15681@raven.dms.auburn.edu> <200310100327.h9A3REl20310@raven.dms.auburn.edu> <200310150138.h9F1cWg10456@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1066314464 32633 80.91.224.253 (16 Oct 2003 14:27:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Oct 2003 14:27:44 +0000 (UTC) Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Oct 16 16:27:42 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AA96M-0004F0-00 for ; Thu, 16 Oct 2003 16:27:42 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AA96L-0006MI-00 for ; Thu, 16 Oct 2003 16:27:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AA8vJ-0003BE-UO for emacs-devel@quimby.gnus.org; Thu, 16 Oct 2003 10:16:17 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AA8qx-0001vl-5T for emacs-devel@gnu.org; Thu, 16 Oct 2003 10:11:47 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AA8pn-0001WQ-Fd for emacs-devel@gnu.org; Thu, 16 Oct 2003 10:11:00 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AA8pl-0001Ve-1n for emacs-devel@gnu.org; Thu, 16 Oct 2003 10:10:33 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.24) id 1AA8mI-0003mI-Hl; Thu, 16 Oct 2003 10:06:58 -0400 Original-To: Luc Teirlinck In-reply-to: <200310150138.h9F1cWg10456@raven.dms.auburn.edu> (message from Luc Teirlinck on Tue, 14 Oct 2003 20:38:32 -0500 (CDT)) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:17153 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17153 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.