From: David Capello <davidcapello@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Avoid asking to user for lock (ask-user-about-lock)
Date: Thu, 24 Sep 2015 18:33:54 -0300 [thread overview]
Message-ID: <CA+hc8b5c1nY1LOTbxY1wWyw_LhjtJ2choMncnK1EEVsXuXN-JQ@mail.gmail.com> (raw)
In-Reply-To: <jwvr3lnbk2h.fsf-monnier+INBOX@gnu.org>
On Thu, Sep 24, 2015 at 6:10 PM, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > And it seems to work, but I still getting some messages like:
> > .../.emacs.keyfreq.lock locked by david@pc (pid 9076): (s, q, p, ?)?
> > in the minibuf.
>
> When?
>
When write-region is called by multiple Emacs instances at the same time.
You can try it by yourself with the latest keyfreq master commit, using this
configuration:
(require 'keyfreq)
(setq keyfreq-autosave-timeout 1) ;; I'm using 1 second to test the lock
mechanism
(keyfreq-mode 1)
(keyfreq-autosave-mode 1)
After that you can open two instances and try to write in both of then
quickly random
characters in the scratch buffer (you will need to do it quickly and
switching between
both instances).
- David
next prev parent reply other threads:[~2015-09-24 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 12:39 Avoid asking to user for lock (ask-user-about-lock) David Capello
2015-09-24 15:52 ` Stefan Monnier
2015-09-24 20:42 ` David Capello
2015-09-24 21:10 ` Stefan Monnier
2015-09-24 21:33 ` David Capello [this message]
2015-09-25 1:22 ` Stefan Monnier
2015-09-25 2:08 ` David Capello
2015-09-25 11:05 ` Fwd: " David Capello
2015-10-20 14:20 ` Stefan Monnier
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=CA+hc8b5c1nY1LOTbxY1wWyw_LhjtJ2choMncnK1EEVsXuXN-JQ@mail.gmail.com \
--to=davidcapello@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).