Hi Dominik, > > Sure. Like I said previously, if you want to automate this further > > go right ahead. > > That's not so simple.
I know. That's why I was happy to manually edit the documentation myself. > For the docuementation you use some extra > information that can not be derived from the sources: > > * Whether a command is obsolete or deprecated > * To which logical group the command belongs > * Where to begin a new column on the page with all the commands > (is that the meaning of the "--"-lines?) Correct. > Did I miss anything else? The if-elsif-else-endif syntax patch doesn't fit into this (function table) framework. See: http://article.gmane.org/gmane.comp.window-managers.fvwm.devel/3080 > The first two can be solved by extending the tagging in > functable.c (I'll do that later). But do you have an idea how to > format the big command list automatically, without any manual > editing? Fiddly. See attached Perl script. Don't ask me how it works. :) Strip the '--' lines out of doc/util/cmds.txt & use as input. > > perl may not be the best tool for it though. > > Oh, I am sure perl is perfectly suitable for the task, but many > proprietary UNIX-machines don't have perl. Agreed. Do we really want to make the FVWM build process depend on perl just for a 150 line Perl script? Ciao for now, Scott. :)
verticalLayout.pl
Description: Perl program
