Thanks a lot for the fixes, Matthew!

The workaround was not too much of a problem to set up in the end (the elemref 
were generated by a macro in my case, so I just had to use make-link-element + 
the global variable instead of elemref). I'll probably get rid of it once a new 
version with your fixes ships out.

For what it's worth, I sometimes find it difficult to guess what the complete 
tag with prefixes should be, e.g. in the example above I expected the tag to be

`(elem (prefixable (lib "test-tag-prefix/scribblings/sub.scrbl")
                   "foo"))

but the tag actually is:

`(elem (prefixable "(lib test-tag-prefix/scribblings/test-tag-prefix.scrbl)"
                   "(lib test-tag-prefix/scribblings/sub.scrbl)"
                   "foo"))

I found an awful hack to make scribble print the list of all tags for a package:
1) First install the package as a locally linked package (i.e. using "cd 
/path/to/the-pkg/; raco pkg install" with no arguments)
2) Uninstall the package, using "raco pkg remove the-pkg". This removes the 
package link, but does not clear Scribble's cache containing all the tags in 
all the documentation
3) Re-install the package from git instead of linking it from the local copy 
(make sure the git repo is up-to-date with the local copy), using "raco pkg 
install https://github.com/user/the-pkg.git";. When Scribble renders the 
documentation for this second copy of the package, it still has not cleaned the 
cache of tags, and therefore generates an error message for every single tag 
present in the package, complaining that it is a duplicate.
4) Scribble will continue to print the error messages each time a package is 
recompiled with "raco setup --pkgs some-package". To get rid of them, run: 
"raco setup; raco setup --avoid-main; raco setup --doc-index". If at some point 
all the links on the documentation's start page turn red, fear not (this 
happened to me) and run these three commands again a couple of times, they 
should fix it.

Hopefully I have overlooked some function in the documentation which prints all 
the tags within a package or document (an equivalent of module->exports for 
tags, if you will) and someone will point it out, but until then this hack may 
be useful to others :) .

Regards,
Georges

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to