Hi David! On Do, 06 Aug 2015, David Champion wrote:
> * On 06 Aug 2015, Kevin J. McCarthy wrote: > > Christian Brabandt wrote: > > > Yeah, the sed script is not portable. Better to replace it by perl > > > (patch attached) > > > > Thanks for the patch. Is there any reason you didn't translate > > > - -e 's/??/\?\?/g' \ > > to perl? > > > > dgc, looks like you originally committed this, do you have any comments? > > I tend to avoid perl/python/etc when more basic utilities will do. It's > true that virtually every system has perl preinstalled now, but mutt > is also used on very bare-bones platforms (which is why the C version > exists; there's a C compiler by definition). In general I agree, but on the other hand, it seems to be easier to maintain and also it looks like this is what other projects do as well (e.g. git). > 1. We can support BSD's sed for txt2c.sh. The difference is just that > BSD sed only supports \n a an ascii escape. (Will need literals in the > makefile.) But - What about other seds from other Unices? regards, Christian -- ASCII a stupid question, you get an EBCDIC answer.
