Using the ANSI standard for info-look

Using the ANSI standard for info-look

[Stefan Monnier]

Any objection to the patch below?
It corrects the regexp for Lisp symbols (to be like the one used for elisp),
it corrects the case-sensitivity, and it adds an entry to use the Texinfo
rendition of the ANSI CL standard if available.


        Stefan


--- info-look.el	26 jun 2005 13:52:14 -0400	1.47
+++ info-look.el	26 jun 2005 14:10:45 -0400	
@@ -811,7 +812,11 @@
 
 (info-lookup-maybe-add-help
  :mode 'lisp-mode
- :regexp "[^()'\" \t\n]+"
+ :regexp "[^][()'\" \t\n]+"
+ :ignore-case t
+ ;; The Texinfo rendition of the last draft ANSI standard for Common Lisp
+ ;; (dpANS).  See http://www.ifa.au.dk/~harder/dpans.html
+ :doc-spec '(("(ansicl)Symbol Index" nil nil nil))
  :parse-rule 'ignore
  :other-modes '(emacs-lisp-mode))

Re: Using the ANSI standard for info-look

[Jesper Harder]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> + ;; The Texinfo rendition of the last draft ANSI standard for Common Lisp
> + ;; (dpANS).  See http://www.ifa.au.dk/~harder/dpans.html

Better to use the URL http://purl.org/harder/dpans.html which should
last longer.

-- 
Cheers,
Jesper Harder

Re: Using the ANSI standard for info-look

[Richard M. Stallman]

    Any objection to the patch below?
    It corrects the regexp for Lisp symbols (to be like the one used for elisp),
    it corrects the case-sensitivity, and it adds an entry to use the Texinfo
    rendition of the ANSI CL standard if available.

Please don't add the reference to the ANSI standard.  It is not free.

Deciding when it is proper for GNU software to work with something
non-free that may happen to be installed is subtle.  The boundary line
is not as crisp as one might wish.  But I think this is on the wrong
side of it.

Re: Using the ANSI standard for info-look

[Jesper Harder]

"Richard M. Stallman" <rms@gnu.org> writes:

>     Any objection to the patch below?
>     It corrects the regexp for Lisp symbols (to be like the one used for elisp),
>     it corrects the case-sensitivity, and it adds an entry to use the Texinfo
>     rendition of the ANSI CL standard if available.
>
> Please don't add the reference to the ANSI standard.  It is not free.

True.  Although, it might turn out that /is/ public domain.  According
to Kent Pitman:

  Lars Brinkhoff <lars.s...@nocrew.org> writes:         
  > How about the Common Lisp dpANS documents?  I was under the impression 
  > that they were released under public domainish terms, but now that I 
  > look, I can't find any copyright notice. 

  You're right that there isn't a proper notice per se.  Documents do 
  exist (but are not on display publicly) that would show that the legal 
  intent was to have placed them into the public domain, even though we 
  botched the final execution of that.  A good intellectual property 
  lawyer would tell you that this means the legal status is messy, but 
  what that really means (I believe) is that those who paid for its 
  creation could (hypothetically) have grounds to make a claim that it 
  was encumbered in some way, that is, to assert that they have some 
  right of ownership.  But since all of those parties at one time or 
  another signed into this system of contracts identifying that the 
  intent was to make a public domain document, I don't personally think 
  they would succeed.   

Re: Using the ANSI standard for info-look

[Richard M. Stallman]

    > Please don't add the reference to the ANSI standard.  It is not free.

    True.  Although, it might turn out that /is/ public domain.  According
    to Kent Pitman:

People are trying to talk with the remnants of the committee about
this issue.  If they achieve something, we can take advantage of that.
But that is a long shot; for mow, we must assume the situation will
not change.