| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This is the correct name of the protocol, usage of the word
"WebSockets" should be limited.
|
|
|
|
| |
Bump liberty, it generated incorrect help messages.
|
|
|
|
|
|
|
|
| |
Now that it's functional in both frontends, we can flaunt it.
I still don't want to make it the default.
Closes #1
|
|
|
|
|
| |
https://github.com/open-rpc/client-js also uses WebSockets,
although they don't seem to support notifications (in general).
|
|
|
|
| |
I have consulted `man 7 man-pages` but overall it's a huge mess.
|
|
|
|
|
|
|
|
| |
So that most of the time users won't need to use any switches.
--pretty-print has been inverted into jq's --compact-output,
and --auto-id has been replaced with barely, if-at-all useful
--null-as-id.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I need two renderers to work: hswg/libasciidoc and asciidoctor
in man page mode (and ideally in HTML as well). That should be
covered now.
The triple-plus thing was the first thing that showed good results,
after trying backslashes, single-plus quoting and [] after ://.
The change of the source code block kind could be considered as
unification. I'm combining tabs with spaces within one document
though, and I should get rid of the tabs in the rest of it then...
|
|
Taking some preliminary steps for inclusion in Linux distributions.
The help message has been slightly improved and the README extended,
with part of it now residing in the man page.
One less GNU dependency, for what it's worth.
|