[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] trunk r116304: * lisp/desktop.el (desktop-read): Claim

From: Eli Zaretskii
Subject: Re: [Emacs-diffs] trunk r116304: * lisp/desktop.el (desktop-read): Claim the lock when the owner is not the current process.
Date: Sat, 08 Feb 2014 09:52:05 +0200

> From: Juri Linkov <address@hidden>
> Cc: address@hidden
> Date: Fri, 07 Feb 2014 21:42:00 +0200
> >> +  * desktop.el (desktop-read): Claim the lock when the owner is not
> >> +  the current process.  (Bug#16157)
> >
> > What happens if an Emacs session that locked the desktop file is still
> > alive?
> The one that comes last wins.  The last session will do auto-saving,
> the previous won't.  At least, there should be no conflict of both sessions
> trying to auto-save to the same file, because auto-saving checks the 
> ownership.
> The conflict might occur when during exiting both sessions will try writing
> to the same file.  I see nothing in `desktop-kill' that would prevent saving
> to a non-locked desktop, except the question "Save desktop?"

That's not what I see today, I think.  When I need to test something
in a fresh session, I sometimes by mistake invoke "emacs" instead of
"emacs -Q", which reads my ~/.emacs and activates desktop saving.  The
main Emacs session is alive, of course.  Then, when I exit, I'm asked
whether to save desktop and given the opportunity to say NO, because I
certainly don't want my main desktop file to be overwritten by this
mistaken session.  I'm not sure this change doesn't eliminate this
useful capability.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]