hyperspec.el

Having just been burned painfully by this, I suggest the
following two changes to the hyperspec support:

1.  In the sample emacs file ilisp.emacs, change 

; (setq common-lisp-hyperspec-symbol-table
;       "/home/joe/HyperSpec/Data/Map_Sym.Txt")

to 

; (setq common-lisp-hyperspec-symbol-table
;       "/home/joe/HyperSpec/Data/Map_Sym.txt")

so that the default names match.

2.  In hyperspec.el, the file "Map_Sym.txt" is read in a
    top-level-form starting with

(if common-lisp-hyperspec-symbol-table

I think we should change this to 

(if (file-readable-p common-lisp-hyperspec-symbol-table)

to handle the case where the variable is set, but not to a file that
actually exists, and that we should probably have at least a warning
if common-lisp-hyperspec-symbol-table is not a readable file, as it
seems that it always should be when hyperspec.el is loaded.  As it's
written currently, if you've set common-lisp-hyperspec-symbol-table
incorrectly, it will silently generate an emtpy table for
common-lisp-hyperspec-symbols, which is never what is wanted.  (This
is especially problematic in the context of (1) above).

(Ideally, we might also check to make sure the contents of the file
Map_Sym.txt are what you're expecting (i.e., pairs of lines matching
the list of keys you have), but this is a little more work.)

Cheers,

rif


-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC.  
Does your code think in ink? You could win a Tablet PC. 
Get a free Tablet PC hat just for playing. What are you waiting for? 
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en