From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] ignoring Info extensions Date: Fri, 02 Apr 2004 21:28:23 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <2914-Fri02Apr2004212823+0300-eliz@gnu.org> References: <200404021416.i32EGYj01894@f7.net> <87n05udyze.fsf@mail.jurta.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1080934598 6960 80.91.224.253 (2 Apr 2004 19:36:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 2 Apr 2004 19:36:38 +0000 (UTC) Cc: emacs-devel@gnu.org, janneke@gnu.org, karl@freefriends.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Apr 02 21:36:32 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1B9USu-0007Ou-00 for ; Fri, 02 Apr 2004 21:36:32 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1B9USu-0002pn-00 for ; Fri, 02 Apr 2004 21:36:32 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B9US1-0006pL-2R for emacs-devel@quimby.gnus.org; Fri, 02 Apr 2004 14:35:37 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B9URK-0006nV-K0 for emacs-devel@gnu.org; Fri, 02 Apr 2004 14:34:54 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B9UQo-0006Xh-E2 for emacs-devel@gnu.org; Fri, 02 Apr 2004 14:34:53 -0500 Original-Received: from [192.114.186.24] (helo=legolas.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B9UOc-00064F-OJ; Fri, 02 Apr 2004 14:32:08 -0500 Original-Received: from zaretski ([80.230.154.15]) by legolas.inter.net.il (MOS 3.4.5-GR) with ESMTP id BNS44070; Fri, 2 Apr 2004 21:31:37 +0200 (IST) Original-To: Juri Linkov X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <87n05udyze.fsf@mail.jurta.org> (message from Juri Linkov on Fri, 02 Apr 2004 21:19:17 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 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:21208 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21208 > From: Juri Linkov > Date: Fri, 02 Apr 2004 21:19:17 +0300 > > > eliz> How about if we instead detect the "*Note:*" case and don't > > treat it as a reference? > > > > I believe this amounts to *Note:[^*] (vs. *Note:\s). I think either one > > is ok, it won't make any difference in practice. I slightly tend toward > > the latter, because it is clearer to understand "*Note: is always > > followed by whitespace" rather than "*Note: is followed by anything > > except a *" (which, in practice, is always whitespace). > > I guess you actually meant *Note[^:*] vs. *Note\s. Anyway, > restricting the character after *Note to [:*] instead of > whitespace apparently will not solve the problem for all > known references. Here is the distribution of \*Note[^ \t]+ > matches on the biggest Info base I found: > > 78 *Note:* > 8 *NOTEBOOK, > 6 *Note: > 4 *NOTE:* > 4 *NOTE* > 3 *Note*: > 2 *note:* > 2 *NOTEBOOK) > 2 *NOTE*: > 1 *note* > 1 *Notes:* > 1 *Note2: > 1 *note' > 1 *Note', > > So perhaps whitespace is a better choice. But if we use *Note[^:*], we remain compatible to whatever Info files are out there that don't have a whitespace after "*Note:", right? Isn't that better to solve a problem without breaking what previously worked?