From: Stefan Monnier <monnier@iro.umontreal.ca>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: lock mechanism like in desktop.el
Date: Sun, 30 Aug 2009 15:58:53 -0400 [thread overview]
Message-ID: <jwv8wh18496.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ab1h7k0z.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 30 Aug 2009 11:01:16 +0200")
> desktop.el has a lock mechanism that is independent of external
> programs. I'd prefer such a solution. Maybe the lock mechanism in
> desktop.el could be made more generic (and moved from desktop.el to
> simple.el/files.el?) so that other packages could use it without
> duplicating the code (and loading desktop.el).
We already have such functionality (lock-buffer, unlock-buffer,
file-locked-p), or am I missing something?
Stefan
prev parent reply other threads:[~2009-08-30 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.uywjaz0jq40fbn@balu.cs.uni-paderborn.de>
2009-08-19 16:37 ` accidentally started gnus jidanni
2009-08-25 12:46 ` Dan Christensen
2009-08-29 23:10 ` Tim Landscheidt
2009-08-30 5:17 ` Graham Murray
2009-08-30 9:01 ` lock mechanism like in desktop.el (was: accidentally started gnus) Reiner Steib
2009-08-30 19:58 ` Stefan Monnier [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=jwv8wh18496.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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.
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 NNTP newsgroup(s).