From: Pierre Neidhardt <ambrevar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30421@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#30421: 25.3; desktop.el: Steal lock when no living "emacs" process owns it
Date: Sun, 11 Feb 2018 17:57:29 +0100 [thread overview]
Message-ID: <87mv0f5urq.fsf@gmail.com> (raw)
In-Reply-To: <838tbz1o8k.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
Setting `desktop-load-locked-desktop' works _only if_ I know there is no
other emacs (daemon or not) owning the lock. We still have a conflict
otherwise.
Hence my suggested patch.
It won't work in the scenario Eli mentioned, but I'm not sure how
relevant that is. Isn't better than than generating conflict with local
instance of Emacs?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-02-11 16:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 9:54 bug#30421: 25.3; desktop.el: Steal lock when no living "emacs" process owns it Pierre Neidhardt
2018-02-11 15:50 ` Eli Zaretskii
2018-02-11 16:08 ` Pierre Neidhardt
2018-02-11 16:15 ` Noam Postavsky
2018-02-11 16:32 ` Eli Zaretskii
2018-02-11 16:57 ` Pierre Neidhardt [this message]
2018-02-11 17:18 ` Eli Zaretskii
2018-02-11 17:23 ` Pierre Neidhardt
2018-02-11 18:00 ` Eli Zaretskii
2018-02-11 18:41 ` Pierre Neidhardt
2018-02-11 18:54 ` Eli Zaretskii
2018-02-11 19:01 ` Pierre Neidhardt
2018-02-15 22:56 ` Pierre Neidhardt
2018-02-16 8:11 ` Eli Zaretskii
2018-02-16 22:58 ` Pierre Neidhardt
2018-02-17 7:43 ` Eli Zaretskii
2018-02-18 11:26 ` Pierre Neidhardt
2018-02-18 16:37 ` Eli Zaretskii
2018-02-24 10:39 ` Eli Zaretskii
2018-02-24 19:44 ` Pierre Neidhardt
2018-02-24 20:09 ` Eli Zaretskii
2018-03-03 11:33 ` Eli Zaretskii
2018-03-03 18:05 ` Pierre Neidhardt
2018-03-10 11:52 ` Eli Zaretskii
2018-03-19 11:06 ` Pierre Neidhardt
2018-03-19 12:47 ` Eli Zaretskii
2018-03-19 13:09 ` Pierre Neidhardt
2018-02-11 20:40 ` Richard Stallman
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=87mv0f5urq.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=30421@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.