From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Capello <davidcapello@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Avoid asking to user for lock (ask-user-about-lock)
Date: Thu, 24 Sep 2015 17:10:15 -0400 [thread overview]
Message-ID: <jwvr3lnbk2h.fsf-monnier+INBOX@gnu.org> (raw)
In-Reply-To: <CA+hc8b5=aQ8=enZ-Ky-xLxNykb9Zi7Fxu1iJt4nth66a2jxfug@mail.gmail.com> (David Capello's message of "Thu, 24 Sep 2015 17:42:13 -0300")
> 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?
Stefan
next prev parent reply other threads:[~2015-09-24 21:10 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 [this message]
2015-09-24 21:33 ` David Capello
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=jwvr3lnbk2h.fsf-monnier+INBOX@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=davidcapello@gmail.com \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).