[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: David Kastrup
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 11:47:41 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Juri Linkov <address@hidden> writes:

>>> 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,
> When you invoke "emacs" instead of "emacs -Q" by mistake,
> it warns you about the mistake by asking
>   "Warning: desktop file appears to be in use by PID %s.
>    Using it may cause conflicts.  Use it anyway? "
> so you could just say NO.

It will still want to _save_ the desktop even if you answer No to
loading it.

David Kastrup

reply via email to

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