> myGUIMailViewer /dev/stdin < "$TMPFILE" The reason for this weirdness (instead of myGUIMailViewer "$TMPFILE") is that it's a flatpak program that can't access the normal system $TMPDIR, without taking many detours, so that is kind-of a hack.
> Your diagnostics is wrong, it has nothing to do with startup time. You Just reporting the viewer's error: `parse() => no message` After digging into its source (https://github.com/alescdb/mailviewer), I think it's a case of `mail-parser-rs` not handling streams gracefully. If it doesn't get as many bytes as it wants when it wants them, it errors out. So not a mutt issue at all, but thank you for the reply. JS On 2025-07-31 11:25, Nicolas George wrote: > Jason Stewart via Mutt-users (HE12025-07-31): > > 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. > > Your diagnostics is wrong, it has nothing to do with startup time. You > can try with nedit, whose startup time is pretty much instantaneous, > instead of chrome or thunderbird. > > > > I am working around this with a shell script that quickly saves to a > > tempfile before the pipe busts, > > I remember there is a program that already does that. I thought sponge > from moreutils was it, but I was wrong. > > > > myGUIMailViewer /dev/stdin < "$TMPFILE" > > Two and a half questions to help you figure it out: > > (1) Did you put that “/dev/stdin” in your command line when you piped > from mutt? > > (1') If he answer to (1) is “no”, then what do you think it achieves > to pipe something to chrome or thunderbird? > > (2) When you write either “input_command | command /dev/stdin” or > “command /dev/stdin < input_file”, does the target of /dev/stdin have > the same type? > > Regards, > > -- > Nicolas George
