From: Juanma Barranquero <lekktu@gmail.com>
To: Juri Linkov <juri@jurta.org>
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, 8 Feb 2014 21:29:06 +0100 [thread overview]
Message-ID: <CAAeL0SQK6nJGApYkUY9ERT1Xj3rJzkEY13WewVDwKkvoBbgf=Q@mail.gmail.com> (raw)
In-Reply-To: <87mwi1l7sf.fsf@mail.jurta.org>
On Sat, Feb 8, 2014 at 8:32 PM, Juri Linkov <juri@jurta.org> wrote:
> Then instead of asking a question we could add two new values
> to `desktop-load-locked-desktop'
>
> ask-and-lock -- ask the user and lock the desktop.
> load-and-lock -- load and lock anyway.
>
> with the default to `ask-and-lock'. Whereas the existing
>
> t -- load anyway.
> ask -- ask the user.
>
> will load without locking.
Seems OK.
> I guess your code to detect a running Emacs instance is not too reliable
> to include to desktop.el?
Alas, no. It's Windows-specific, and depends on the fact that I know I
won't have a lock from a remote Emacs instance, and that all my
instances are launched from executables called emacs.exe.
J
next prev parent reply other threads:[~2014-02-08 20:29 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 [this message]
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
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='CAAeL0SQK6nJGApYkUY9ERT1Xj3rJzkEY13WewVDwKkvoBbgf=Q@mail.gmail.com' \
--to=lekktu@gmail.com \
--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).