Are there any timeouts related to <pipe-message>? When I pipe to a
simple program (like `less`), everything works as expected. When I pipe
to a program with a longer startup time, (like `thunderbird` or
`chrome`), there is nothing to read from /dev/stdin.
I am working around this with a shell script that quickly saves to a
tempfile before the pipe busts, but it feels like a hack because I don't
actually know what is going on.
Example Script:
> #!/bin/sh
>
> # Create a temporary file and store its path in a variable
> TMPFILE=$(mktemp) || { echo "Failed to create temporary file." >&2; exit 1; }
> cat > "$TMPFILE"
>
> # Set up a trap to delete the temporary file when the script exits (normally
> or due to error)
> trap 'rm -f "$TMPFILE"' EXIT
> echo "Our temporary file is: $TMPFILE"
>
> myGUIMailViewer /dev/stdin < "$TMPFILE"
thx
JS
