On 9/21/06, Ben Stiglitz <[EMAIL PROTECTED]> wrote: > The major blocking issue was that many manpages have very long > descriptions of first switches, and the first sentence of the > description (which I was clipping to) often doesn't properly describe > the option's effect. The completion was inside a GUI, so it wasn't > too terrible for us to show the whole description, but inside of a > shell this obviously wouldn't be ideal.
I am guessing that semi-automatic approaches might be best here. I have not played with Doclifter, but I assume it would be easy to write a script to output completion code. Then two approaches are: 1. The script writes completion code using the first sentence of every option. The completions are published. Gradually, users edit them and publish their improvements. 2. The scropt writes completion code using the whole description of each option. Right away, the user uses a text editor to delete most of the description text and summarize the long ones. I think both of these are faster and easier than reading each description from the man page and summarizing it; and faster than copy-pasting and editing. (1) has the benefit that you have completions for all commands right away, although they may be of poor quality to start with. Conversely (2) produces higher-quality completions, but more slowly. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
