Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extraneous output #2

Closed
ghost opened this issue Mar 27, 2015 · 3 comments
Closed

extraneous output #2

ghost opened this issue Mar 27, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Mar 27, 2015

The extraneous output (colors, > and < characters) makes it very hard to use this program with other programs that expect unmodified data from stdin and stdout:

$ wscat -c ws://localhost:8081/sync 

connected (press CTRL+C to quit)

< 6

<���0"/�
+["55e06327e530a87a3f21f1f852681dc1","sync"]
> 

This makes it difficult for me to take the data and feed it into another program. For example, here I've got forkdb running in the browser and I would like to sync that to a forkdb running on the server using just stdin and stdout but the line numbers, colors, status logging, and decoration gets in the way of that use case.

This is very un-like netcat, which just provides a raw undecorated stream on stdin and stdout.

In the mean time, I whipped up wsnc but I think it would be better for this package to remove decoration.

@nwwells
Copy link
Collaborator

nwwells commented Jan 24, 2017

Rather, how about a raw mode, as I've found it useful to have the colors and extra output.

@nwwells
Copy link
Collaborator

nwwells commented Feb 21, 2017

Fixed in a2ae4f5 and 2de4e0f. Will be released with 1.2.0 (see #35)

At least the output is. If streaming input into wscat would be beneficial, please open a new issue.

@nwwells nwwells closed this as completed Feb 21, 2017
@nwwells
Copy link
Collaborator

nwwells commented Feb 21, 2017

If streaming input into wscat would be beneficial, please open a new issue.

Actually, #4 will cover handling stdin properly.

FGasper pushed a commit to FGasper/wscat that referenced this issue May 12, 2019
Show code and reason for non-1000 close events from server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant