On Fri, Mar 25, 2005 at 08:09:19PM -0600, Kenneth Pronovici wrote: > _________________________________________ > / Please document in manpage or \ > | /usr/share/doc/polygen what polygen | > \ sources are available and what they do. / > ----------------------------------------- > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || > > It was a rather cool command-line you posted to -curiosa, but I was > disappointed that I had to dig around in /usr/share to see what sources > other than pythoniser were available. Could you please document them > either in a file in /usr/share/doc/polygen, or in the manpage? Based on > the manpage, I expected 'polygen' with no arguments to give me a list, > but it didn't.
You are totally right. The ideal thing would be that polygen with no arguments gives a list of what's around. However, I don't know if upstream is interested in that, as polygen is mainly used in their website which has a different grammar database than /usr/share/polygen. And I can't code it myself as I'm quite bad with ocaml :) The best option so far would be to auto-generate a polygen-data manpage with a list of what's available. I could do that at package build time using the metadata found in the grammar: that'd be fun, even! :) I could then link such a manpage from the polygen manpage. Do you like this option? See anything better? Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature