Enrico Forestieri wrote: > > 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.
ok thats better than -e lyx example... > > 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 as i said i accept both 2 or 3 but will strongly opose to 1 since it not only changes the behaviour but also make impossible for anybody to reuse old scripts without revisiting each of them. since its pretty clear that you are strongly against 2 and me against 1 i propose 3 so we can stop the flamewar. pavel
