From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Ulrich Mueller" <ulm@gentoo.org>
Cc: emacs-pretest-bug@gnu.org, emacs@gentoo.org,
1474@emacsbugs.donarmstrong.com,
Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: bug#1474: 23.0.60; desktop.el don't check if pid in his lock file is always in use
Date: Wed, 3 Dec 2008 10:16:43 +0100 [thread overview]
Message-ID: <f7ccd24b0812030116r3facbbbau9b098fcb9e47c81d@mail.gmail.com> (raw)
In-Reply-To: <18742.19976.920879.266804@a1ihome1.kph.uni-mainz.de>
On Wed, Dec 3, 2008 at 10:14, Ulrich Mueller <ulm@gentoo.org> wrote:
> So in addition to the process id, the lock file should also contain
> the host name, so that the most common usage case can be handled.
That's an idea worth pursuing.
> And instead of a lock file with new syntax, couldn't desktop.el use a
> symlink, identical to what is done for file locking? (Or even use
> functions "lock-buffer" etc.?)
Only if you want to remove functionality for users of Emacs on Windows.
Juanma
next prev parent reply other threads:[~2008-12-03 9:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 21:43 bug#1474: 23.0.60; desktop.el don't check if pid in his lock file is always in use Thierry Volpiatto
2008-12-02 22:39 ` Juanma Barranquero
2008-12-03 6:36 ` Thierry Volpiatto
2008-12-03 8:25 ` Juanma Barranquero
2008-12-03 8:47 ` Thierry Volpiatto
2008-12-03 9:15 ` Juanma Barranquero
2008-12-03 10:08 ` Thierry Volpiatto
2008-12-03 10:20 ` Juanma Barranquero
2008-12-03 21:27 ` Stefan Monnier
2008-12-03 9:14 ` Ulrich Mueller
2008-12-03 9:16 ` Juanma Barranquero [this message]
2008-12-02 22:52 ` Stefan Monnier
2008-12-02 23:06 ` Ulrich Mueller
2008-12-03 6:30 ` Thierry Volpiatto
2020-01-24 16:47 ` Stefan Kangas
2020-02-08 14:23 ` Stefan Kangas
2020-02-08 15:20 ` Eli Zaretskii
2020-04-27 10:34 ` Stefan Kangas
2020-04-27 14:50 ` Eli Zaretskii
2022-03-24 8:25 ` bug#1474: bug#25232: 24.4; Eliminate - Warning: Desktop file appears to be " Lars Ingebrigtsen
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=f7ccd24b0812030116r3facbbbau9b098fcb9e47c81d@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=1474@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=emacs@gentoo.org \
--cc=thierry.volpiatto@gmail.com \
--cc=ulm@gentoo.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).