On Mon, Aug 8, 2016, at 12:52 PM, [email protected] wrote: > I don't think it will be fruitful to enter into any further debates.
Perhaps not. > > However: > > >> I see halcmd as something like grep. It runs from the command line, > >> and its documentation should be available from the command line. > > >> But "man halcmd" doesn't work, and that seems to be a policy > >> decision by machinekit leadership. I simply cannot agree with that > >> decision. Such is life. > > "mank halcmd" DOES work on the command line. And how is the user to know that the answer is mank? The need to use mank is not discoverable by a user unless he happens to read just the right paragraph on just the right page of the machinekit website. > > *'Anything related to machineKit, add a K'** * I did consider the > feasibility of having an 'interception script' via /etc/alternatives > for man, to fork machinekit display requests one way and normal man > pages another. However since there is no Machinekit distro and > machinekit could be installed on any kind of linux distro, that was not > going to be achievable without a lot of bother and undoubted breakages. Is it impossible to generate traditional manpages (viewable by "man") from the asciidoc sources? > I don't think typing one extra letter is too bad a compromise. Try it. It's not typing the letter that's the problem. Its knowing that you need to type the letter. You're probably right - neither of us is going to convince the other. -- John Kasunich [email protected] -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
