- hyperspec-lookup-devel@lists.common-lisp.net

[hyperspec-lookup-devel] [PATCH] better defaults for the Map_Sym.txt and Mop_Sym.txt files
by Luís Oliveira 08 Dec '09

08 Dec '09

Hello, The attached patch hopefully provides better default pathnames for the Mop_Sym.txt file and the Map_Sym.txt provided you include it in the distribution as well. (Which would probably be a good idea.) Thanks, -- Luís Oliveira http://r42.eu/~luis/

1 1

[hyperspec-lookup-devel] Hyperdoc integration with hyperspec-lookup
by David Lichteblau 25 Dec '08

25 Dec '08

Hi, wanting to try hyperdoc, I found a patch for hyperspec-lookup in hyperdoc. Here are my questions: 1. (question for Erik, as hyperspec-lookup maintainer:) hyperspec-lookup doesn't build unless the hyperspec is already installed, because it looks for files in /usr/. Would it be possible to commit the diff in hyperdoc, which simply adds Map_Sym.txt to the distribution, allowing hyperspec-lookup to build and function without a local installation of the hyperspec as a pre-requisite? A patch is here: http://repo.or.cz/w/hyperspec-lookup.git?a=commitdiff;h=f79a65bcb96262532ec… This would be important for me, because I'd like my projects to depend on hyperdoc, which depends on hyperspec-lookup, and I believe that the user experience would suffer a lot if asdf-install failed on all computers that don't happen to have the Debian package `hyperspec' installed. 2. (question for Nikodemus, who wrote hyperspec-lookup.patch:) There's another part in that diff which adds a hyperdoc-lookup function to the HS package, but actually looks up CL symbols. I didn't apply this part, because I could not understand its purpose. It also seems outdated: hyperdoc currently passes only two arguments, not three. Is this part important? 3. (question for Nikodemus and/or Rudi, who seems to be the only person with actual commit access to hyperdoc on common-lisp.net) Even after changing the above, lookup of CL symbols through hyperdoc didn't work for me, because introspective lookup signals an error on packages without hyperdoc support, so lookup can't fall through to the hyperspec-lookup case. I changed this locally. Patch: http://repo.or.cz/w/hyperdoc.git?a=commitdiff;h=03638747a633caec1034a423732… To get things running, I made git mirrors of the two projects and committed my changes there. Would it be possible to commit the changes upstream? http://repo.or.cz/w/hyperspec-lookup.git http://repo.or.cz/w/hyperdoc.git Thanks, d.

1 0

[hyperspec-lookup-devel] Please move your files off ofcommon-lisp.net FTP
by eenge＠common-lisp.net 07 Aug '06

07 Aug '06

As mentioned in http://common-lisp.net/pipermail/users/2006-August/000006.html FTP will soon be going away on common-lisp.net. Your project showed up in a grep for ftp in your public_html suggests that you either store files in your ftp directory or that you link to files in FTP on common-lisp.net. This email serves as a second notice that you'll want to update your links and move your files. Move them into your public_html directory and link to them there, Apache will happily serve them for you. Thanks, Erik.

1 0

[hyperspec-lookup-devel] Auto-nag: hyperspec-lookup link verifier failed
by root＠common-lisp.net 18 Jan '06

18 Jan '06

You are being nagged on because your project's name showed up in the nightly Checkbot run. Checkbot checks for broken links etc. This probably means that you are either pointing to a broken link or that someone is pointing to a broken link on your site. Or something else, it check's a bunch of stuff. Update your webpages or you shall be nagged again next week. To find out what's wrong with your webpages, please consult: http://common-lisp.net/checkbot/checkbot-common-lisp.net.html Any questions? You can reach the author of this cronjob at admin(a)common-lisp.net Thanks!

1 0

[hyperspec-lookup-devel] Hyperdoc directions (fwd)
by Nikodemus Siivola 24 Apr '04

24 Apr '04

Apparently I wasn't subscribed, so the original bounced. 'ere we go: ---------- Forwarded message ---------- Date: Sat, 24 Apr 2004 23:59:15 +0300 (EEST) From: Nikodemus Siivola <tsiivola(a)kosh.hut.fi> To: slime-devel(a)common-lisp.net Cc: Edi Weitz <edi(a)agharta.de>, Daniel Barlow <dan(a)telent.net>, stig(a)users.sourceforge.net, hyperspec-lookup-devel(a)common-lisp.net Subject: Hyperdoc directions First some background to get everyone up to speed: Hyperdoc is a project to provide CLHS-style documentation lookup for libraries. http://www.common-lisp.net/project/hyperdoc/ Edi Weitz recently added support for the hyperdoc protocol to his packages, and the hyperdoc CVS contains horrid buggy hack in slime.patch which replaces the clhs lookup in Slime by similar functionality powered by hyperdoc. (Hyperdoc delegates undocumented symbols to hyperspec-lookup <http://www.common-lisp.net/project/hyperspec-lookup/>.) Calling (hyperdoc:lookup package-name symbol-name &optional doc-type-name) gives either NIL, an URI, or if multiple docs for the same symbol exist an alist of the form ((doc-type-name . uri)*). The URIs related to a package can be stared in files, and if this has been done with (hyperdoc:generate-index package), then lookup can be done even if the package is not loaded. The idea is that these lookup files could also be used directly by Slime/Emacs if it isn't connected to a lisp. In it's current state it's basically usable, but some refinements are probably necessary for serious use: 1) Hook the index generation to compiling, either by doing (eval-when (:compile-toplevel) (when (find-package :hyperdoc) (funcall (intern "GENERATE-INDEX" :hyperdoc) :this-package))) in client packages, or maybe/preferebly this could be delegated to ASDF. 2) Do the Emacs/Slime binding: * If connected use hyperdoc. * If not connected use the indices and hyperspec.el. * When the query gives multiple results (eg. a structure and a function of the same name) prompt the user to choose which type of documentation should be fetched. "Fair enough, but get to the point already!" Ok, ok... Do people have ideas/opinions on number 1? Once it is done, I think essentially all work on the CL side is complete. Then, if desired, the API can be integrated with cl:documentation or asdf:hyperdocumentation. What do Slime folks think of the Emacs integration? Is someone willing to do the grunt work on it? As the patch to current Slime shows, my elisp-fu and slime-fu are rather lacking. Anything I've forgotten? Cheers, -- Nikodemus

1 0