Dixit Ricardo Mones <[EMAIL PROTECTED]> : > > Hi! > Hello
> > [environment variables not interpreted anymore] > > Sorry, but I think I've overlooked this (minor) bug too much ;-) > Oh yeah, I forgot about this :-) > Is this still happening in current sylpheed-claws-gtk2? (2.5.6) > I just tested on a more up-to-date machine with the 2.5.6 version (not the one I'm writing this message with), the "bug" is still happening. I used double-quotes because it is less a bug and more like a change of behaviour. I guess the passage from sylpheed-claws 1.x to 2.5.x would only surprise Sarge users when doing the upgrade, and still, only if they use envt variables and shell-interpretable characters in the command producing the signature. So, in summary, the bug is still there, and a workaround is for instance calling a shell with the command. For instance, if the command was (I just tested) : cat $HOME/.signature && cat ~/.signature2 && echo $USER it becomes : bash -c "cat $HOME/.signature && cat ~/.signature2 && echo $USER" if you use bash. The problem with this workaround can be that the shell launched from sylpheed-claws might not have all the variables sylpheed-claws sees, and it might not even be the default shell of the user. Regards, Samuel Colin -- Nice cat BTW, Neo looks a bit like a norvegian or a maine coon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
