From: Juri Linkov <juri@jurta.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
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 12:35:41 +0200 [thread overview]
Message-ID: <87bnyhops2.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAAeL0ST7YtXB+qGM1_7BZ6ohdrAUv8DA-e0Uxd1NvFCQdiPmWw@mail.gmail.com> (Juanma Barranquero's message of "Sat, 8 Feb 2014 11:21:51 +0100")
>> The problem was that when a session crashes, all subsequent sessions
>> can't auto-save the desktop since they didn't take the lock
>> from the crashed session.
>
> Surely I'm missing something, but what good is the lock if subsequent
> sessions can steal it even if the corresponding Emacs is still
> running?
Maybe we need a separate question in addition to the existing question
1. "Warning: desktop file appears to be in use by PID %s.
Using it may cause conflicts. Use it anyway? "
something like
2. "Claim the lock from PID %s to take the ownership of the desktop file? "
next prev parent reply other threads:[~2014-02-08 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.190526.1391788637.10747.emacs-diffs@gnu.org>
2014-02-07 16:20 ` [Emacs-diffs] trunk r116304: * lisp/desktop.el (desktop-read): Claim the lock when the owner is not the current process Eli Zaretskii
2014-02-07 19:42 ` Juri Linkov
2014-02-07 20:25 ` Juanma Barranquero
2014-02-08 10:11 ` Juri Linkov
2014-02-08 10:21 ` Juanma Barranquero
2014-02-08 10:35 ` Juri Linkov [this message]
2014-02-08 10:42 ` Juanma Barranquero
2014-02-08 19:32 ` Juri Linkov
2014-02-08 20:29 ` Juanma Barranquero
2014-02-08 21:08 ` Juanma Barranquero
2014-02-08 7:52 ` Eli Zaretskii
2014-02-08 10:14 ` Juri Linkov
2014-02-08 10:47 ` David Kastrup
2014-02-08 10:52 ` Eli Zaretskii
2014-02-08 11:16 ` Andreas Schwab
2014-02-08 14:22 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bnyhops2.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.