Jim Porter <jporterbugs@gmail.com> writes:
The attached patch resolves the issue for me, but I'm not sure if it's
the best strategy. If possible, I think it would be better for
`eshell-parse-external-pipeline' to solely focus on finding the
external pipe operators ("*|", "*<", and "*>")[1] and then for
`eshell-rewrite-external-pipeline' to prepare the command string to
pass to sh. This would also have the advantage[2] of making it
possible to support a richer set of Eshell features with external
pipes, such as the following:
I think that sounds like a good idea (but I don't use eshell regularly,
so I don't really have much of an opinion here). Perhaps John does;
added to the CCs.