From xemacs-m  Sun Feb 23 19:55:28 1997
Received: from mailhost.lanl.gov (mailhost.lanl.gov [128.165.3.12])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id TAA11446
	for <xemacs-beta@xemacs.org>; Sun, 23 Feb 1997 19:55:27 -0600 (CST)
Received: from branagh.ta52.lanl.gov (branagh.ta52.lanl.gov [128.165.144.9]) by mailhost.lanl.gov (8.8.5/8.8.3) with SMTP id SAA07769 for <xemacs-beta@xemacs.org>; Sun, 23 Feb 1997 18:55:28 -0700 (MST)
Received: by branagh.ta52.lanl.gov (SMI-8.6/SMI-SVR4)
	id SAA20451; Sun, 23 Feb 1997 18:51:32 -0700
Date: Sun, 23 Feb 1997 18:51:32 -0700
Message-Id: <199702240151.SAA20451@branagh.ta52.lanl.gov>
From: "John A. Turner" <turner@branagh.ta52.lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: xemacs-beta@xemacs.org
Subject: 19.15-b95 - same problems as b93, b94
In-Reply-To: <199702170520.WAA11993@branagh.ta52.lanl.gov>
References: <199702170520.WAA11993@branagh.ta52.lanl.gov>
Reply-To: turner@lanl.gov

Previously I wrote:

 > o Reported back for b93 that I'd be going along fine, and then all of
 >   a sudden everything would hit a brick wall.  Just going to the *shell*
 >   buffer and typing pwd would take 30 seconds or so, with the CPU
 >   pegged.
 > 
 >   Switching to a new frame would take 15-20 seconds to redraw.

[snip]

 >   I was busy, so I just switched back to b90.  Would sure like to know
 >   if anyone else is seeing anything like this.
 > 
 >   Note that it doesn't happen right from the start.  It goes along
 >   fine for a bit, and then wham, right into a wall.

OK, I'm still seeing this in b95.

I've been commenting out pieces of my startup stuff to try and pin it
down, since originally I couldn't get it to happen with -q.  Finally
got somewhere though.

Here's the minimum I can do and get it to happen:

o xemacs -q
o load-file .xemacs-options
o M-x shell
o C-x C-f .emacs

When I switch back to *shell* and type pwd RET, the CPU pegs and it
takes about 30 seconds for the command to complete.  After this the
whole thing is useless.  Even C-x C-c takes about that long to
complete.

The file I visit can be anything, basically.  I'm thinking it's just
something to turn on font-lock or something.

Remember, this started after b90; never happened before.

Any ideas what to suspect as the culprit in .xemacs-options?

-- 
John Turner
http://www.lanl.gov/home/turner

