[TriLUG] How to debug piping issues

[Reid Thompson via TriLUG]

Just wondering, did you try that command without the --file? My man page
example for stdin doesn't have it.

On Sun, Mar 27, 2016, 23:24 Brian via TriLUG <trilug at trilug.org> wrote:

> On 03/27/2016 12:13 AM, Steven Tardy wrote:
> >
> >> On Mar 26, 2016, at 11:33 PM, Brian via TriLUG <trilug at trilug.org>
> wrote:
> >>
> >> $ zbarcam --raw | xdotool type --file -
> >
> > Typical buffering, probably have to send 4kB before the second program
> sees anything. Google suggests "unbuffer" may prevent the pipe from
> buffering.
> >
>
> $ unbuffer zbarcam --raw | xdotool type --file -
>
> No difference :-(
>
> Plus it seems as though if 4k buffering were the issue, my perl script
> (run this way: zbarcam --raw | barwedge.pl ) would have the same
> problem, and it doesn't.
>
> Maybe there's something about how xdotool type --file - expects the
> stdin file handle to behave (perhaps it doesn't type anything until it
> sees an EOF or something).
>
> Anyway, thanks!
> -B
>
>
> --
> This message was sent to: jreidthompson at gmail.com <jreidthompson at gmail.com
> >
> To unsubscribe, send a blank message to trilug-leave at trilug.org from that
> address.
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web  :
> http://www.trilug.org/mailman/options/trilug/jreidthompson%40gmail.com
> Welcome to TriLUG: http://trilug.org/welcome