json doesn't integrate with piping commands
hroptatyr opened this issue · 3 comments
hroptatyr commented
freundt@clyde:pts/10:~> json -o data -u < /tmp/foo | head
7.26
7.475
7.47
7.575
7.35
7.35
7.575
7.41
7.55
7.63
node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: EPIPE, Broken pipe
at Socket._writeImpl (net.js:159:14)
at Socket._writeOut (net.js:444:25)
at Socket.write (net.js:377:17)
at [object Object].processObjects (/home/freundt/usr/lib/jsonCommand.js:388:24)
at [object Object].<anonymous> (/home/freundt/usr/lib/jsonCommand.js:443:40)
at [object Object].emit (events.js:64:17)
at [object Object]._emitData (fs.js:914:29)
at afterRead (fs.js:898:10)
at wrapper (fs.js:245:17)
zpoley commented
thanks for using json-command and submitting this issue. could you please provide more details? i'm not exactly sure what you're trying to do, or what is going on here. thanks.
hroptatyr commented
I'm sorry the markdown has completely mangled the actual bug report, I'm going to clarify. I edited the original report, so things should be clear now.
zpoley commented
Thanks to tricknotes for fixing this issue with this commit!