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: Mon, 13 Oct 2003 01:03:05 -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> <200310120334.h9C3Ygk26986@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1066021879 3163 80.91.224.253 (13 Oct 2003 05:11:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 13 Oct 2003 05:11:19 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Oct 13 07:11:12 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 1A8uzA-0004kd-00 for ; Mon, 13 Oct 2003 07:11:12 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1A8uzA-0004Xl-00 for ; Mon, 13 Oct 2003 07:11:12 +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 1A8uvy-0006AU-Ry for emacs-devel@quimby.gnus.org; Mon, 13 Oct 2003 01:07:54 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1A8uur-00069x-QS for emacs-devel@gnu.org; Mon, 13 Oct 2003 01:06:45 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1A8uuK-00060q-U3 for emacs-devel@gnu.org; Mon, 13 Oct 2003 01:06:44 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1A8uuK-00060l-Kf for emacs-devel@gnu.org; Mon, 13 Oct 2003 01:06:12 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.24) id 1A8urJ-0006ua-3s; Mon, 13 Oct 2003 01:03:05 -0400 Original-To: Luc Teirlinck In-reply-to: <200310120334.h9C3Ygk26986@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 11 Oct 2003 22:34:42 -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:17056 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17056 In as far as the first one goes, one could replace the occurrences of [ \t\n]+ and [ \t\n]* (the latter probably would have to be changed to [ \t\n]+ anyway, for consistency) in my patch by [ \n]. (If one does not allow multiple spaces, it seems consistent not to allow tab either.) That would mean that the author would have to be careful about "space related sloppiness" like trailing whitespace or an inadvertent inappropriate double space inside a sentence. That is true. I am not sure which approach would actually do a better job in practice. Just in case, what about a convention to follow ;;; by a single space if one wants the line two be considered a "heading line" by outline-minor-mode and by at least two spaces if one wants it to be considered a "body line". That might work. If you use M-x comment-region on code within a function, there will normally be at least three spaces after the semicolons. However, if you use M-x comment-region to comment out top-level code, there may sometimes be just one space. Still, making outlines use this convention might be a good improvement in outline processing on Lisp files. (I think that outline processing on Lisp files is a rather obscure issue.)