all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 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 16:22:38 +0200	[thread overview]
Message-ID: <83eh3dwuoh.fsf@gnu.org> (raw)
In-Reply-To: <8761opsvls.fsf@igel.home>

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Juri Linkov <juri@jurta.org>,  emacs-devel@gnu.org
> Date: Sat, 08 Feb 2014 12:16:15 +0100
> 
> 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?

What if the PID is reused?

Yes, we could cater to all these, if we want.  But not using even the
PID seems too sloppy, IMO.



      reply	other threads:[~2014-02-08 14:22 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
2014-02-08 14:22             ` Eli Zaretskii [this message]

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=83eh3dwuoh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=schwab@linux-m68k.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 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.