unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ben Wing" <ben_wing@hotmail.com>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, ben@666.com, bws@deepcopy.org,
	xemacs-design@xemacs.org, emacs-devel@gnu.org
Subject: Re: Profiling font-lock in xemacs
Date: Sat, 29 Jun 2002 12:34:18 -0700	[thread overview]
Message-ID: <afl27q$up2$2@main.gmane.org> (raw)




>From: Richard Stallman <rms@gnu.org>
>Reply-To: rms@gnu.org
>To: ben_wing@hotmail.com
>CC: monnier+gnu/emacs@rum.cs.yale.edu, ben@666.com, bws@deepcopy.org,   
>xemacs-design@xemacs.org, emacs-devel@gnu.org
>Subject: Re: Profiling font-lock in xemacs
>Date: Sat, 29 Jun 2002 02:41:06 -0600 (MDT)
>
>It would be better not to have a delay of even .25 second in handling
>C-g.  It ought to respond crisply.

of course, this is only on systems without SIGIO, where we have no choice 
but to implement such a thing.

>
>If the delay were made smaller, eventually it would be insignificant.
>I don't know at what point that is reached.

.25 second is pretty small.  the smaller you go, of course, the more cpu 
time you potentially use up.


>
>Currently on some systems C-g handling can involve a delay of up to 1
>second, the wait for "polling for input".  That's because when it was
>implemented there was no better facility to use than `alarm'.
>Nowadays I gather there is one; we should change the polling interval
>to something shorter than a second.

setitimer() on unix systems.





_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

             reply	other threads:[~2002-06-29 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29 19:34 Ben Wing [this message]
     [not found] <F102hm4mRK4dGDNhxKL00000226@hotmail.com>
2002-06-29  8:41 ` Profiling font-lock in xemacs Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-06-27 21:55 Ben Wing
     [not found] <200205300129.17083.bws@deepcopy.org>
     [not found] ` <87d6vet7f2.fsf@tleepslib.sk.tsukuba.ac.jp>
     [not found]   ` <5l3cw9lob0.fsf@rum.cs.yale.edu>
     [not found]     ` <200205301939.02926.bws@deepcopy.org>
     [not found]       ` <005d01c21835$344dc340$0201a8c0@neeeeeee>
     [not found]         ` <200206201517.g5KFHaw07020@rum.cs.yale.edu>
     [not found]           ` <009301c218f1$8e5a9040$0201a8c0@neeeeeee>
     [not found]             ` <200206211911.g5LJBvN12715@rum.cs.yale.edu>
     [not found]               ` <026d01c21991$ede47580$0201a8c0@neeeeeee>
2002-06-22 17:32                 ` Stefan Monnier
2002-06-23  4:53                   ` Stephen J. Turnbull
2002-06-23 18:12                   ` Richard Stallman
     [not found]                   ` <200206231812.g5NICe024443@aztec.santafe.edu>
2002-06-23 18:40                     ` Stefan Monnier
     [not found]                     ` <200206231840.g5NIeaa30522@rum.cs.yale.edu>
2002-06-24 19:39                       ` Richard Stallman
     [not found]                       ` <200206241939.g5OJdsk26260@aztec.santafe.edu>
2002-06-24 20:04                         ` 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='afl27q$up2$2@main.gmane.org' \
    --to=ben_wing@hotmail.com \
    --cc=ben@666.com \
    --cc=bws@deepcopy.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=xemacs-design@xemacs.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).