From owner-ntemacs-users@june  Thu Oct 10 10:35:29 1996
X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	[nil "Thu" "10" "October" "1996" "18:28:54" "+0100" "Nico Francois" "nico.francois@scala.nl" nil "29" "High-priority Emacs" "^From:" nil nil "10" nil nil nil nil]
	nil)
Received: from joker.cs.washington.edu (joker.cs.washington.edu [128.95.1.42]) by june.cs.washington.edu (8.7.6/7.2ju) with SMTP id KAA10432 for <voelker@june.cs.washington.edu>; Thu, 10 Oct 1996 10:35:28 -0700
Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by joker.cs.washington.edu (8.6.12/7.2ws+) with ESMTP id KAA28342 for <voelker@joker.cs.washington.edu>; Thu, 10 Oct 1996 10:35:26 -0700
Received: from postduif.scala.nl (postduif.scala.nl [194.183.111.130]) by june.cs.washington.edu (8.7.6/7.2ju) with ESMTP id JAA04850 for <ntemacs-users@cs.washington.edu>; Thu, 10 Oct 1996 09:23:58 -0700
Message-Id: <199610101623.JAA04850@june.cs.washington.edu>
Received: from homer ([194.183.111.152]) by postduif.scala.nl           (post.office MTA v1.9.3 ID# 0-13670) with SMTP id AAA341           for <ntemacs-users@cs.washington.edu>;           Thu, 10 Oct 1996 18:23:34 +0100
Comments: Authenticated sender is <nico@postduif.scala.nl>
Organization: Scala Computer Television
Reply-to: nico.francois@scala.nl
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.42a)
From: "Nico Francois" <nico.francois@scala.nl>
To: ntemacs-users@cs.washington.edu
Subject: High-priority Emacs
Date: Thu, 10 Oct 1996 18:28:54 +0100

I don't know how much this has annoyed anybody else, but if you are 
doing heavy-duty stuff in the background NTEmacs becomes almost 
unbearably sluggish.

Well, I got so fed up with this that I downloaded the source, added a 
single

    SetPriorityClass (GetCurrentProcess(), HIGH_PRIORITY_CLASS);

to an appropriate spot in w32fns.c and recompiled.

This worked perfectly.  Running as a high-priority process Emacs no 
longer suffers from the aforementioned sluggishness as it gets enough 
CPU cycles when you are working with it.  Joy! :)

And when you are not using Emacs it is idle anyway, so it doesn't 
matter that it has a high priority (0% CPU time is the same at every 
priority :-).

Could this (perhaps optionally) be included in 19.35 ?  What are the
views of others about this ?

IMHO this change has no big drawbacks.  Yeah, fine, if font-lock is
fontifying your buffer it will potentially suck up some more CPU
time than normal, but I can live with that. 

                                _o
   Nico Francois                 #>    Sr. Software Engineer
   <nico.francois@scala.com>     4     Scala Computer Television