On Wed, Jul 14, 2010 at 06:41:13PM +0200, Pavel Sanda wrote: > Enrico Forestieri wrote: > > On Wed, Jul 14, 2010 at 10:16:19AM -0400, Julien Rioux wrote: > > > It is hard to believe that you would /inadvertently/ use the command > > > line. If you do, then it was your mistake. But wary users could have > > > a shortcut: alias lyx='lyx -f=none' > > > > I think you're missing the point, too. On July 14 you import the .tex > > file. On July 20 you try to export to latex from command line. Export > > fails because you had forgotten that the original file was still there. > > You investigate and say "gosh, I had left there the original file, luckily > > LyX saved my day" :) > > > > > I vote for 2 (in case users get a vote). > > > > Then, I think you will like the env var approach that lets you live > > as dangerously as you like :) > > he would write 3 in that case, its almost the same ;) > > there are two distinct points to be distinguished: > > 1. to allow users to be where they want - either on the safe side or > on the danger side. both your patches satisfy this. > > 2. to setup the implicit behaviour, when the user didn't choose > anything. > > i think nobody has problem with 1. > both opinions on point 2. have their up and downs, from what i distilled: > > args from the safety side: > - you can lost some data > > args from the danger side: > - the real complaint we ever got is fixed, by "main". the exports to .tex > and .lyx can happen but they seem to be fabricated just for this discussion. > - we break compatility for launching lyx in batch jobs. part of it is repaired > by proposed patches. since Juergen gave red flag for 1.6.7, we are lost > anyway, > thats why i'm not so vocal anymore :) > - its pretty standard that linux command line tools are on the danger side by > default > even when they allow globbing etc... > > feel free to add points on safe side ;)
I did not imagine I could have caused such a reaction for a safety measure that I thought could have been quite easily overcomed. I am going to do nothing until a *clear* consensus emerges about what should be the default behavior when exporting from command line. I think it boils down to: 1) Never ovewrite files, unless explicitely told so 2) The main file should be always overwritten -- Enrico
