Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Alkor San
    @alkorsan
    in fact a hate command lines that hide the info and you have to read all the short description to know that there is more. but some command lines do this
    there is not a lot of flags , why hide them?
    and this flag is needed for the simple mode --linemode-retain-newlines, i see it s hiding!
    Vitaly Shukela
    @vi

    Because of there are (or will be) many tricky flags that may confuse users.

    Obviously, --long-help and the fact that some flags and options (and later address types) are hidden is mentioned in the help message.
    Try websocat --help.

    --linemode-retain-newlines shouldn't be needed much. Just slap -l on server side part and it would also look more nice.
    Line mode on client should correspond to line mode on server.
    Alkor San
    @alkorsan
    oh i did not know
    I think it s better to have them in the --help not in the --long-help, they don t confuse me , it is the description what confused me in most of the time. the description says something and the flag do more things of what it is told.
    Alkor San
    @alkorsan
    I feel like that you write the description supposing things , and i think the help should not need suppositions but it should show you things without more fiddeling or asking in forums
    Vitaly Shukela
    @vi
    Would just a list of hidden options and flags in --help suffice?
    Alkor San
    @alkorsan
    sorry i did n t get the question, how? you mean to make a list of the hidden flags without description for exemple?
    Vitaly Shukela
    @vi
    One-line list of short and long options. Like (there are hidden options: --linemode-retain-newlines, --dump-spec, .... See --long-help)
    Alkor San
    @alkorsan
    it will make the help very verbose with info that will never be read. but it s better . and what i prefer is leave the flags as they were (there is few ones only) and make better description for them , and hide the specifiers only
    Vitaly Shukela
    @vi
    For example FFmpeg also shows only part of options on usual --help.
    Alkor San
    @alkorsan
    maybe because he have 1 million option :/ and it make it very hard
    even reading the manual of ffmpeg is very hard and tedious
    Vitaly Shukela
    @vi
    Especially about FFmpeg expression evaluator...
    Alkor San
    @alkorsan
    yes I always end up looking for help externally
    Vitaly Shukela
    @vi
    It it a good idea to make --short-help instead with flag and option hiding?
    Alkor San
    @alkorsan
    it will never be used I think, I don t see any use
    --long-help works like man this is the expected
    Vitaly Shukela
    @vi
    Manual page would be generated from --long-help or source code somehow.
    Alkor San
    @alkorsan
    yes
    easier to update too
    Vitaly Shukela
    @vi
    Implemented the --server and --binary options (after unrelated internal refactoring)
    Also now it defaults to --text, --line (this option has actually gone) and --linemode-retain-newlines (also gone).
    Alkor San
    @alkorsan
    wow I will test them all good thank you
    and come back with the results
    Vitaly Shukela
    @vi
    Now there is also --buffer-size and more lints (for advanced mode) and some fixes.
    Alkor San
    @alkorsan
    great options
    Vitaly Shukela
    @vi
    Now improving the documentation.
    Alkor San
    @alkorsan
    good a lot of things changed and strange things happening and 1000 question i have :/ the documentation will help
    Vitaly Shukela
    @vi
    It would be basically reformatted and fixed a bit existing documentation, not a Websocat Book.
    Alkor San
    @alkorsan
    ah ok
    please what does this error mean? or I open an issue for this?
    WARN 2018-07-03T19:20:09Z: websocat::broadcast_reuse_peer: A client's sink is NotReady for start_send
    I couldn t make things work with new updates
    Vitaly Shukela
    @vi
    It means client that is connected to a simple server is too slow for reading responses (or there is some other issue).
    Maybe just make simple server mode websocat -s 1234 accept only one simultaneous connection?
    Alkor San
    @alkorsan
    im not using websocket server but chrome server
    Vitaly Shukela
    @vi
    What is your use case for broadcast-reuse: overlay then?
    Alkor San
    @alkorsan
    it was working but now i removed -l and i got those errorq
    Vitaly Shukela
    @vi
    Anyway discussing the error without showing the full command line here is rather pointless.
    Alkor San
    @alkorsan
    I use broadcast-reuse: only in the exemple you gaves to me using nc
    ok
    I will update the same issue to continue there
    Vitaly Shukela
    @vi
    Pushed major README update. Please review.
    Alkor San
    @alkorsan
    ok thank you
    Vitaly Shukela
    @vi
    There are still remaining "specifier" term usages, but that ubiquitous as before.
    Your Chromium example is included as one of opener README examples.