From: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org, rms@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: jit-lock timer etc.
Date: Tue, 22 Aug 2006 00:22:26 +0200 [thread overview]
Message-ID: <44EA3222.9050405@gmx.at> (raw)
In-Reply-To: <87fyfpq5wf.fsf@stupidchicken.com>
[-- Attachment #1: Type: text/plain, Size: 2708 bytes --]
> Each time Emacs becomes idle, `jit-lock-stealth-fontify' is called;
> with this patch, it requeues itself as a non-idle timer until it
> finishes fontifying. What happens if Emacs becomes idle again before
> fontification finishes? (This may happen if jit-lock-stealth-time is
> very short, or if a timer or process filter makes Emacs idle.) It
> seems to me that this will set off another series of non-idle timers,
> which is not what we want.
> I think that if jit-lock-stealth-fontify is called with no argument,
> and fontification is proceeding, it should do nothing.
Not really. `buffer-list' may have changed in between and I have to
recalculate `jit-lock-stealth-buffers'. I also should care about the
liveness of my buffers here. Anyway your reasoning is valid, I could
pile up a sequence of timers all working on the same possibly stale
version of `jit-lock-stealth-buffers'. Sooner or later they should stop
but that's no justification for what I wrote.
> One way to do
> this is to introduce a new `jit-lock-stealth-fontifying' variable.
> (This may not work well if stealth fontification is so slow that the
> buffer list changes significantly before fontification finishes, but I
> think there's not much we can do about this.)
I'll simply use another timer.
> Now the nitpicks. First, jit-lock-stealth-buffers should be
> defvar'ed.
It _was_ in my first patch. Please convince yourself that I'm not
completely imbecile.
> Second, this part is rather hard to read:
>
> (let (....
> load-delay)
> (when (or (not jit-lock-stealth-load)
> (or (<= (car (load-average)) jit-lock-stealth-load)
> (not (setq load-delay t))))
> ...))
> I suggest changing it to
>
> (let (...
> (load-delay (and jit-lock-stealth-load
> (>= (car (load-average)) jit-lock-stealth-load))))
> (when (not load-delay)
> ...))
>
I want to call myself with a zero delay when there's nothing to fontify
in the car of `jit-lock-stealth-buffers' and there are buffers left.
But you're right, obviously.
> Finally, is it really necessary to test jit-lock-stealth-time here?
> If it's invalid, jit-lock-stealth-fontify wouldn't get called in the
> first place.
>
> (when (and jit-lock-stealth-buffers jit-lock-stealth-time)
> (run-at-time
> (if load-delay jit-lock-stealth-time (or jit-lock-stealth-nice 0))
> nil 'jit-lock-stealth-fontify t))
>
Paranoia. The user could have set this to nil in between two calls.
Emacs timers are vindictive.
> Other than that, I think this proposal is good.
Not much left, I suppose. Please look again at the new patch.
[-- Attachment #2: jit-lock.patch --]
[-- Type: text/plain, Size: 5626 bytes --]
*** jit-lock.el.~1.54.~ Mon Aug 21 14:35:24 2006
--- jit-lock.el Tue Aug 22 00:14:42 2006
***************
*** 444,513 ****
result))))
! (defun jit-lock-stealth-fontify ()
"Fontify buffers stealthily.
! This functions is called after Emacs has been idle for
! `jit-lock-stealth-time' seconds."
! ;; I used to check `inhibit-read-only' here, but I can't remember why. -stef
! (unless (or executing-kbd-macro
memory-full
! (window-minibuffer-p (selected-window)))
! (let ((buffers (buffer-list))
! (outer-buffer (current-buffer))
minibuffer-auto-raise
! message-log-max)
! (with-local-quit
! (while (and buffers (not (input-pending-p)))
! (with-current-buffer (pop buffers)
! (when jit-lock-mode
! ;; This is funny. Calling sit-for with 3rd arg non-nil
! ;; so that it doesn't redisplay, internally calls
! ;; wait_reading_process_input also with a parameter
! ;; saying "don't redisplay." Since this function here
! ;; is called periodically, this effectively leads to
! ;; process output not being redisplayed at all because
! ;; redisplay_internal is never called. (That didn't
! ;; work in the old redisplay either.) So, we learn that
! ;; we mustn't call sit-for that way here. But then, we
! ;; have to be cautious not to call sit-for in a widened
! ;; buffer, since this could display hidden parts of that
! ;; buffer. This explains the seemingly weird use of
! ;; save-restriction/widen here.
!
! (with-temp-message (if jit-lock-stealth-verbose
! (concat "JIT stealth lock "
! (buffer-name)))
!
! ;; In the following code, the `sit-for' calls cause a
! ;; redisplay, so it's required that the
! ;; buffer-modified flag of a buffer that is displayed
! ;; has the right value---otherwise the mode line of
! ;; an unmodified buffer would show a `*'.
! (let (start
! (nice (or jit-lock-stealth-nice 0))
! (point (point-min)))
! (while (and (setq start
! (jit-lock-stealth-chunk-start point))
! ;; In case sit-for runs any timers,
! ;; give them the expected current buffer.
! (with-current-buffer outer-buffer
! (sit-for nice)))
!
! ;; fontify a block.
(jit-lock-fontify-now start (+ start jit-lock-chunk-size))
! ;; If stealth jit-locking is done backwards, this leads to
! ;; excessive O(n^2) refontification. -stef
! ;; (when (>= jit-lock-context-unfontify-pos start)
! ;; (setq jit-lock-context-unfontify-pos end))
!
! ;; Wait a little if load is too high.
! (when (and jit-lock-stealth-load
! (> (car (load-average)) jit-lock-stealth-load))
! ;; In case sit-for runs any timers,
! ;; give them the expected current buffer.
! (with-current-buffer outer-buffer
! (sit-for (or jit-lock-stealth-time 30))))))))))))))
!
\f
;;; Deferred fontification.
--- 444,507 ----
result))))
! (defvar jit-lock-stealth-buffers nil
! "List of buffers that should be fontified stealthily.")
!
! (defvar jit-lock-stealth-repeat-timer nil
! "Timer for repeated stealth fontification.")
!
! (defun jit-lock-stealth-fontify (&optional repeat)
"Fontify buffers stealthily.
! This function is called repeatedly after Emacs has become idle for
! `jit-lock-stealth-time' seconds. Optional argument REPEAT is expected
! non-nil in a repeated invocation of this function."
! (unless (or (input-pending-p)
! executing-kbd-macro
memory-full
! (window-minibuffer-p (selected-window))
! (null (if repeat
! ;; In repeated invocations `jit-lock-stealth-buffers'
! ;; has been already set up.
! jit-lock-stealth-buffers
! ;; In first invocation set up `jit-lock-stealth-buffers'
! ;; from `buffer-list'.
! (setq jit-lock-stealth-buffers (buffer-list)))))
! (when (timerp jit-lock-stealth-repeat-timer)
! ;; Cancel timer for repated invocations.
! (cancel-timer jit-lock-stealth-repeat-timer))
! (let ((buffer (car jit-lock-stealth-buffers))
minibuffer-auto-raise
! message-log-max
! start delay)
! (if (and jit-lock-stealth-load
! (> (car (load-average)) jit-lock-stealth-load))
! ;; If load is too high, run again after `jit-lock-stealth-time'
! ;; seconds.
! (setq delay jit-lock-stealth-time)
! (if (buffer-live-p buffer)
! (with-current-buffer buffer
! (if (and jit-lock-mode
! (setq start (jit-lock-stealth-chunk-start (point))))
! ;; Fontify one block of at most `jit-lock-chunk-size'
! ;; characters.
! (with-temp-message (if jit-lock-stealth-verbose
! (concat "JIT stealth lock "
! (buffer-name)))
(jit-lock-fontify-now start (+ start jit-lock-chunk-size))
! ;; Run again after `jit-lock-stealth-nice' seconds.
! (setq delay (or jit-lock-stealth-nice 0)))
! ;; Nothing to fontify here. Remove this buffer from
! ;; `jit-lock-stealth-buffers' and run again immediately.
! (setq delay 0)
! (setq jit-lock-stealth-buffers (cdr jit-lock-stealth-buffers))))
! ;; Buffer is no more live, remove it from `jit-lock-stealth-buffers'
! ;; and run again instantaneously.
! (setq delay 0)
! (setq jit-lock-stealth-buffers (cdr jit-lock-stealth-buffers))))
! (when (and jit-lock-stealth-buffers jit-lock-stealth-time)
! ;; Call us again.
! (setq jit-lock-stealth-repeat-timer
! (run-at-time delay nil 'jit-lock-stealth-fontify t))))))
\f
;;; Deferred fontification.
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2006-08-21 22:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 11:12 jit-lock timer etc Richard Stallman
2006-08-21 11:39 ` Kim F. Storm
2006-08-21 16:57 ` martin rudalics
2006-08-21 18:51 ` Chong Yidong
2006-08-21 22:22 ` martin rudalics [this message]
2006-08-21 23:26 ` Chong Yidong
2006-08-22 7:18 ` Kim F. Storm
2006-08-22 15:41 ` Richard Stallman
2006-08-23 12:27 ` martin rudalics
2006-08-23 13:09 ` Kim F. Storm
2006-08-24 5:20 ` Richard Stallman
2006-08-24 7:47 ` Kim F. Storm
2006-08-24 7:58 ` Kim F. Storm
2006-08-24 9:07 ` Kim F. Storm
2006-08-24 14:47 ` Chong Yidong
2006-08-25 20:23 ` Richard Stallman
2006-08-25 22:45 ` Kim F. Storm
2006-08-25 20:23 ` Richard Stallman
2006-08-25 21:27 ` Chong Yidong
2006-08-26 12:22 ` Richard Stallman
2006-08-24 9:10 ` Kim F. Storm
2006-08-24 12:23 ` martin rudalics
2006-08-24 12:54 ` Kim F. Storm
2006-08-24 13:07 ` Kim F. Storm
2006-08-24 13:11 ` Kim F. Storm
2006-08-24 13:34 ` Kim F. Storm
2006-08-24 18:11 ` martin rudalics
2006-08-24 20:11 ` Kim F. Storm
2006-08-24 23:41 ` Chong Yidong
2006-08-25 7:17 ` Kim F. Storm
2006-08-24 14:16 ` Chong Yidong
2006-08-24 5:20 ` Richard Stallman
2006-08-24 7:48 ` Kim F. Storm
2006-08-24 12:21 ` martin rudalics
2006-08-24 15:27 ` Chong Yidong
2006-08-24 15:40 ` Chong Yidong
2006-08-24 18:09 ` martin rudalics
2006-08-24 19:16 ` Stefan Monnier
2006-08-24 19:20 ` Stefan Monnier
2006-08-24 16:18 ` martin rudalics
2006-08-24 16:34 ` Chong Yidong
2006-08-24 19:48 ` Chong Yidong
2006-08-25 6:00 ` martin rudalics
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=44EA3222.9050405@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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).