On Sat, Apr 22, 2017 at 10:35:04PM +0200, Vincent Lefevre wrote: > > So wait, what? Mutt is now filtering out environment variables when > > it spawns MIME handlers, filters, etc.? That seems pretty broken. > > This is not what Kevin said. A setenv() *in Mutt* is not sufficient > to export the variable to child processes. The envlist needs to be > updated too. See:
Ah OK, that makes more sense... Although, I don't really get why Mutt needs a feature for this, when you can just set the environment variables in... the environment. Before starting Mutt. I'd imagine only a handful of people will use this feature, and if they *really* *really* must insist on setting environment variables only in Mutt that other programs in their login session won't see, probably they should've just used a shell script to set them and start Mutt. But given the code is already in I guess there's not much harm. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgpm1CB9dH_Xq.pgp
Description: PGP signature
