unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juri Linkov <juri@jurta.org>, 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:16:15 +0100	[thread overview]
Message-ID: <8761opsvls.fsf@igel.home> (raw)
In-Reply-To: <83ob2hx4eq.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 Feb 2014 12:52:29 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Isn't it safer to see of the PID that locked the desktop file still
> runs, and if so, ask for permission?

What if the other instance runs on a different host?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2014-02-08 11:16 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761opsvls.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).