Le dimanche 26 juin 2016, 11:46:05 D. Michael McIntyre a écrit : > On 06/26/2016 06:44 AM, Yves Guillemot wrote: > > If there is only one user on this computer and if the RG files are stored > > on a local file system it should be a safe workaround to add in > > .bash_profile something like: > > find ~ -name ".~lock.*.rg#" | xargs rm -f > > I have an ancient laptop at my drum kit that I use to ssh -X into my > main box from across the room. I can have the same .rg file open on the > same filesystem on the same computer as the same user.
In such a case there are two users, one on the main computer and one on the laptop, even if they share the same user-id (and even if they are the same person) and you are right, the lockfile should not be blindly removed at login. > A handy ignore button is probably the most reasonable thing to offer so > users can deal with the issue with minimal irritation. Maybe a smart > ignore button that at least checks for likely suspects before presenting > itself. Is this the only instance? Is this a local only filesystem? > Yes and yes? Show ignore button. > Probably a good solution. Some times ago I was so bothered by the lockfile while trying to fix a crash that I made a bash alias from the above command to be able to quickly clear the lock. Yves ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
