From: Leo Liu <sdl.web@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: 13999@debbugs.gnu.org
Subject: bug#13999: 24.3.50; rng-validate-while-idle -> (error "Selecting deleted buffer")
Date: Sat, 23 Mar 2013 22:13:11 +0800 [thread overview]
Message-ID: <m1ip4inr0o.fsf@gmail.com> (raw)
In-Reply-To: <F273797D-110A-4BCF-A1B6-13CFF9E3D452@tzi.org> (Carsten Bormann's message of "Sat, 23 Mar 2013 08:54:08 +0100")
On 2013-03-23 15:54 +0800, Carsten Bormann wrote:
> Well, how do you test that...
> I played around with background-validating an XML file, scrolling
> while that happens, and that seems to work.
> I don't use stealthy jit-lock etc., though, and my XML files are of
> moderate size (couple hundred kB), so maybe I'm not in the target
> group addressed by the original hack.
>
> It seems really solving the problem the code was trying to address
> would require having a priority scheme for idle timer work: Validation
> happens in idle time but may be higher priority than other idle timer
> work. Another way of blocking other idle timer work while doing
> sit-for/input-pending-p would, of course, also help; this might need
> exposing the READABLE_EVENTS_DO_TIMERS_NOW flag from input-pending-p
> and sit-for.
>
> Grüße, Carsten
OK thanks for the information. I use nxml even less. I only use it to
edit plist files on OSX which are small in general. So I'll assume it is
good enough.
Leo
next prev parent reply other threads:[~2013-03-23 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 15:35 bug#13999: 24.3.50; rng-validate-while-idle -> (error "Selecting deleted buffer") Carsten Bormann
2013-03-19 15:55 ` Leo Liu
2013-03-19 20:51 ` Stefan Monnier
2013-03-20 0:33 ` Leo Liu
2013-03-20 3:29 ` Stefan Monnier
2013-03-20 4:30 ` Leo Liu
2013-03-22 9:55 ` Leo Liu
2013-03-22 13:36 ` Stefan Monnier
2013-03-22 14:39 ` Leo Liu
2013-03-22 17:34 ` Stefan Monnier
2013-03-23 1:47 ` Leo Liu
2013-03-23 7:54 ` Carsten Bormann
2013-03-23 14:13 ` Leo Liu [this message]
2013-03-23 3:28 ` Leo Liu
2013-03-23 16:10 ` Stefan Monnier
2013-03-24 6:51 ` Leo Liu
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=m1ip4inr0o.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=13999@debbugs.gnu.org \
--cc=cabo@tzi.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).