You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As new channels have started appearing it's once again becoming obvious that the lack of nmsg documentation is slowing down adoption. While nmsgtool does produce a splash page of options, it lacks examples showing the correct combination of commands/syntax, the required support libraries, where to obtain those libraries and how to read the nmsg binary files with C and python.
I don't consider "source code" as documentation. :)
In summary, documentation regarding nmsg and nmsgtool would be greatly appreciated.
Andy
The text was updated successfully, but these errors were encountered:
you are of course correct. let me know if you're aware of a contract
tech writer. we need "man3" pages.
deteque wrote:
As new channels have started appearing it's once again becoming
obvious that the lack of nmsg documentation is slowing down adoption.
While nmsgtool does produce a splash page of options, it lacks
examples showing the correct combination of commands/syntax, the
required support libraries, where to obtain those libraries and how to
read the nmsg binary files with C and python.
I don't consider "source code" as documentation. :)
In summary, documentation regarding nmsg and nmsgtool would be greatly
appreciated.
Andy
—
Reply to this email directly or view it on GitHub #3.
As new channels have started appearing it's once again becoming obvious that the lack of nmsg documentation is slowing down adoption. While nmsgtool does produce a splash page of options, it lacks examples showing the correct combination of commands/syntax, the required support libraries, where to obtain those libraries and how to read the nmsg binary files with C and python.
I don't consider "source code" as documentation. :)
In summary, documentation regarding nmsg and nmsgtool would be greatly appreciated.
Andy
The text was updated successfully, but these errors were encountered: