Enrico Forestieri wrote: > > could you elaborate why strong disagreement? another utils i'm currently > > using > > around lyx work also like that - pdflatex rewrites ouput, dvips too. you are > > strongly disagree with their doing also? > > its really no fun to scan all the scripts in various projects manually > > checking > > usages of lyx calls and be worried what has been overlooked. so i would like > > to hear that strong argument why we change this. > > Neither pdflatex, nor dvips will ever destroy your input file, would they? > Instead, LyX can do that. Try "lyx -e lyx foo.lyx" and your input file > will be overwritten, updated to the current version and your old input > file is no more.
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. 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 ;). > > the user bug report was asking for slightly different thing - not > > overwriting > > figure accompanying the lyx file. thats dataloss and needed to be fixed > > indeed, > > but overwriting .pdf result is completely different issue. > > So, we should check each format in order to decide what to do? If you have > a gun, I suggest that you keep it discharged. > > Anyway, would the attached patch be enough for you? When you don't specify > the -f switch, the preference settings are used when exporting from the > command line. However, in order to keep the gun discharged, I added the > "none" option for -f (I don't like living dangerously). yes, it would be good enough to keep my mouth shut up. 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 :) pavel
