On Wed, Jul 14, 2010 at 03:50:50AM +0200, Pavel Sanda wrote: > > you really mean "lyx -e lyx foo.lyx" seriously? :) its just pretty normal that > if you ask on command line to write output over the input file it gets > overwritten > like the infamous 'cat file1 file2 > file1' mistake. don't see the swith in > pdflatex > but "dvips file.dvi -o file.dvi" will of course overwrite input - and thats > correct.
While it is clear from your cat or dvips examples that the input file is going to be overwritten, this is not the case in my lyx example. > commands can be changed if they are wrong, but the exotic case invented just > for > this debate like "lyx -e lyx foo.lyx" is hardly enough reason. > it looks as fixing acrobatic usecases never reported by anybody for > the price of introducing new problems. typical usecase is output to dvi/ps/pdf > so the question about some real problem our previous scheme causes to users > remains (except the fixed issue with overwriting eps figure ;). I think you don't get the principle. You import a .tex file in lyx, then you inadvertently use "lyx -e latex" on that file. Your original file would now be gone. > i still maintain that the backward compatibility will cause less user's > frustration for this particular switch (ie default RC setting would need to be > set on main file overwrite) than new gun-discharged-course but i let the > responsibility on Juergen or anybody else who want to comment on :) So, let's have a poll: 1) Leave things as they are (need -f to overwrite) 2) The main file should always be overwritten 3) If no -f switch is given, use preferences settings for overwriting I vote for 1) -- Enrico
