From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: fortran-fill-paragraph fails Date: Fri, 29 Dec 2006 16:06:57 -0500 Message-ID: References: <87d56acfod.fsf@lrde.org> <17810.43383.385509.776556@tfkp07.physik.uni-erlangen.de> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1167426908 12406 80.91.229.10 (29 Dec 2006 21:15:08 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 29 Dec 2006 21:15:08 +0000 (UTC) Cc: =?iso-8859-1?Q?Micha=EBl?= Cadilhac , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 29 22:15:06 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1H0P49-0005n6-3G for ged-emacs-devel@m.gmane.org; Fri, 29 Dec 2006 22:15:01 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H0P48-0007Ls-HW for ged-emacs-devel@m.gmane.org; Fri, 29 Dec 2006 16:15:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H0P3p-0007IN-By for emacs-devel@gnu.org; Fri, 29 Dec 2006 16:14:41 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H0P3o-0007GD-E1 for emacs-devel@gnu.org; Fri, 29 Dec 2006 16:14:40 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H0P3o-0007Fr-8C for emacs-devel@gnu.org; Fri, 29 Dec 2006 16:14:40 -0500 Original-Received: from [83.228.189.52] (helo=alfajor.home) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H0OwO-0005Uo-02 for emacs-devel@gnu.org; Fri, 29 Dec 2006 16:07:00 -0500 Original-Received: by alfajor.home (Postfix, from userid 20848) id 05BFD1CD5D; Fri, 29 Dec 2006 16:06:57 -0500 (EST) Original-To: "Roland Winkler" In-Reply-To: <17810.43383.385509.776556@tfkp07.physik.uni-erlangen.de> (Roland Winkler's message of "Wed\, 27 Dec 2006 18\:12\:23 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.91 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:64441 Archived-At: >> > (commark >> > (comment-string-strip (buffer-substring comstart comin) nil t)) >> > (comment-re >> > ! (if (string-match comment-start-skip (concat "\0" commark "a")) >> > (concat "[ \t]*" (regexp-quote commark) >> > ;; Make sure we only match comments that use >> > ;; the exact same comment marker. >> >> Please add a clear comment explaining the reason for this "\0". > I must admit that this patch goes much beyond my knowledge of elisp > hacking. Also, I cannot find anything in the elisp manual explaining > the meaning of "\0" in this context. If there is a general idea for > this, I'd much appreciate if it was documented in the elisp manual, > too. (Or did I look at the wrong spot?) There's nothing specific to elisp there, and the \0 is just some arbitrary char: a space would have probably worked just as well. Stefan