From: karl@freefriends.org (Karl Berry)
Cc: juri@jurta.org, janneke@gnu.org, emacs-devel@gnu.org
Subject: Re: [PATCH] ignoring Info extensions
Date: Fri, 2 Apr 2004 19:19:39 -0500 [thread overview]
Message-ID: <200404030019.i330JdU08775@f7.net> (raw)
In-Reply-To: <2914-Fri02Apr2004212823+0300-eliz@gnu.org>
juri> I guess you actually meant *Note[^:*] vs. *Note\s. Anyway,
Yes, sorry.
eliz> But if we use *Note[^:*],
That won't fix all of the cases Juri found:
> 8 *NOTEBOOK,
> 1 *Notes:*
> 1 *Note2:
> 1 *note'
These would still be misidentified as references. So according to these
findings, it would have to be *Note[^:*Bs2'], and obviously some day
there will be some other character. Let's fix it for real, right now,
by saying *Note is followed by whitespace.
we remain compatible to whatever Info files
are out there that don't have a whitespace after "*Note:", right?
But there aren't any, I feel more sure than ever. Every Info writer
writes "*Note " for references. So let's reflect that in the Info readers.
I see no problem here.
Isn't that better to solve a problem without breaking what previously
worked?
As a general rule, I of course agree with you. As you know, I am a bear
for compatibility, and we have tried our utmost never to break old Info
readers with new Info files. I think the last time we did was with
@anchor, umpteen years ago.
However, in this particular case, it seems to me that the proposed
change (a) would not break old Info files that would break, and (b) it
fixes the original problem, of references being misidentified, for good
(as well as we can, anyway), whereas the alternative does not.
Therefore, I believe that
\*[Nn]ote[ \t\n]
is preferable to
\*[Nnote][^anything]
Let's do it. I will change the Info reader.
Thanks,
k
next prev parent reply other threads:[~2004-04-03 0:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 19:47 resend: [PATCH] ignoring Info extensions Jan Nieuwenhuizen
2004-03-14 7:39 ` Eli Zaretskii
2004-03-14 12:53 ` Jan Nieuwenhuizen
2004-03-29 7:57 ` Jan Nieuwenhuizen
2004-03-31 20:56 ` Juri Linkov
2004-04-01 2:01 ` Karl Berry
2004-04-01 5:53 ` Eli Zaretskii
2004-04-01 16:33 ` Juri Linkov
2004-04-01 19:53 ` Eli Zaretskii
2004-04-02 3:27 ` Juri Linkov
2004-04-02 7:47 ` Eli Zaretskii
2004-04-03 1:30 ` Richard Stallman
2004-04-02 1:50 ` Karl Berry
2004-04-02 3:32 ` Juri Linkov
2004-04-02 14:16 ` Karl Berry
2004-04-02 18:19 ` Juri Linkov
2004-04-02 19:28 ` Eli Zaretskii
2004-04-02 21:38 ` Juri Linkov
2004-04-03 0:19 ` Karl Berry [this message]
2004-04-02 19:29 ` Eli Zaretskii
2004-04-02 7:43 ` Eli Zaretskii
2004-04-02 21:47 ` Juri Linkov
2004-04-03 1:25 ` Karl Berry
2004-04-03 4:56 ` Juri Linkov
2004-04-03 9:05 ` Eli Zaretskii
2004-04-03 23:39 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200404030019.i330JdU08775@f7.net \
--to=karl@freefriends.org \
--cc=emacs-devel@gnu.org \
--cc=janneke@gnu.org \
--cc=juri@jurta.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.