I am having a look at this now. Richard
On 11/13/2015 01:55 PM, Scott Kostyshak wrote: > On Fri, Nov 13, 2015 at 05:14:06PM +0000, Guillaume Munch wrote: >> Le > 13/11/2015 17:01, Scott Kostyshak a écrit : >>> On Fri, Nov 13, 2015 at 04:39:24PM +0000, Guillaume Munch wrote: >>>> Le 13/11/2015 16:30, Scott Kostyshak a écrit : >>>>> On Fri, Nov 13, 2015 at 01:52:34PM +0000, Guillaume Munch wrote: >>>>>> Le 11/11/2015 00:40, Richard Heck a écrit : >>>>>>> commit cc83dfa887ade5ef059d338cbf353d77db926f40 >>>>>>> Author: Richard Heck <rgh...@lyx.org> >>>>>>> Date: Tue Nov 10 12:39:24 2015 -0500 >>>>>>> >>>>>>> Fix bug #9554: When we save a file that was not originally in the current >>>>>>> LyX format, create a backup of the original file. We put it in the backup >>>>>>> directory, if one exists, otherwise in the directory the original file is >>>>>>> in. This is the same strategy as for normal backups. Basically, the only >>>>>>> diferences are: (i) what name we use and (ii) we do not over-write any >>>>>>> backups that may already exist. >>>>>>> >>>>>> >>>>>> >>>>>> I just found a file "varwidth-floats-side-by-side-499.lyx" at the root >>>>>> of my build directory (from where I usually run src/lyx). According to >>>>>> what I had understood this should have been in lib/examples/, where the >>>>>> original file varwidth-floats-side-by-side.lyx has always been, instead. >>>>> >>>>> I would have expected the same. >>>>> >>>>>> My backup dir is set to "". Is there a risk that we are going to pollute >>>>>> all the users ~/ dir with alpha? >>>>> >>>>> We can wait for a reply before releasing alpha. >>>>> >>>> >>>> Not that I incite to delay alpha >>> >>> I see. I misunderstood then. In that case I will proceed because having >>> extra backups floating around is not a horrible bug for an alpha I >>> think. >> >> Given that this can possibly confuse many users (and give bad publicity to >> an useful feature), with the alpha tag I was hoping to encourage a quick >> reply if possible and some quick fix if trivial. This did not happen in the >> very short time frame so now don't hesitate to proceed. >> >> We could mention it in a "known issues" section of the release notes or of >> the wiki, alongside #9362 "Lyx suddenly gets keyboard keys wrong, and >> deadlocks". > > Good idea. Let's wait a bit longer (I want to send a "am I missing > anything obvious" email anyway) and then we will go ahead and mention it > as a known issue and go forward.
