Patch seems reasonable to me.
Please commit to 2.2.x after 2.2.1 is released.
Richard
On 07/07/2016 05:18 AM, José Abílio Matos wrote:
On Thursday, July 7, 2016 10:09:44 AM WEST Andrew Parsloe wrote:
Yes, changing > to -o results in an exported compressed file that 2.1.5
can read. Thanks for the help.
Andrew
Thank you Andrew. I still blame windows for this but in any case to use the
option -o is the right thing to do since we already know where to write. As it
is now lyx2lyx tries to guess where to write it and since no clue is offered
it writes to stdout that then it is written to $$o.
I propose the following patch to go in 2.3 (btw I think we can drop the 2.
prefix from the version ;-) ) and later this could go to 2.2.x (with x >= 2).
The patch makes the call to lyx2lyx less cryptic, e.g. to revert to the 1.3
format we have:
\converter lyx lyx13x "python -tt $$s/lyx2lyx/lyx2lyx -t 221 $$i > $$o" ""
what I propose is that instead of
python -tt $$s/lyx2lyx/lyx2lyx -t 221 $$i > $$o
we can write
python -tt $$s/lyx2lyx/lyx2lyx -V 1.3 -o $$o $$i
or we could write a longer, but more understandable form:
python -tt $$s/lyx2lyx/lyx2lyx --final_version 1.3 --output $$o $$i
FWIW I shuffled the order of the arguments just for the sake of readability,
to let $$i as the last argument.
The funny thing about this is the code is there for almost 8 years. :-)
Regards,
