help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: occasional pause (or stutter) on win32 emacs 23.0.95


From: Livin Stephen
Subject: Re: occasional pause (or stutter) on win32 emacs 23.0.95
Date: Fri, 11 Sep 2009 08:38:33 -0700 (PDT)
User-agent: G2/1.0

On Sep 9, 11:17 pm, egarrulo <egarr...@gmail.com> wrote:
> 2009/9/9 Matthew L Daniel <mdan...@gmail.com>:
>
> > On 2:59 PM, Elena wrote:
>
> >> Same here. Emacs pauses while saving files. I thought it was happening
> >> whenever I had remote files opened, but it ended up not being like
> >> that.
>
> > What specific OS and CPU arch are you experiencing this with?
>
> > And do you have a standard hard drive or SSD?
>
> Only on Windows XP SP3 on x86. Emacs on my Linux box is OK.
>
> Standard hard drive.
>
> I've not used Emacs that much today, but as soon as it shows again,
> I'll try the C-g tip.
>
> Thanks for your attention.


GNU Emacs 23.1.50.1 (powerpc-apple-darwin8.11.0, NS apple-
appkit-824.48)

I've been seeing this same problem for the last month since I compiled
and built emacs on my PowerBook G4 Mac + OS X 10.4.11.

The 'beachball' spins for a few seconds but then emacs works fine
immediately afterwards.
I *have*  tried Ctrl-G, but I don't think it helps: and I would not be
surprised... doesn't the beachball mean 'unresponsive'?

And it is annoyingly frequent :)

To add detail, I'd like to mention that in my case, while I haven't
noticed that this happens more often with C-x C-s.. Will keep an eye
out for this!
steps I use to compile:
0. cvs -z3 -d:pserver:anonymous@cvs.sv.gnu.org:/sources/emacs co emacs
1. ./configure --prefix /Applications/Emacs.app/Contents/MacOS --with-
ns --enable-ns-self-contained=yes --enable-cocoa-experimental-ctrl-
g=yes # NOT 'sure' that used the 'experimental-C-g' option on this
latest build!
2. edit Makefile to remove 'maybe-blessmail'
3. make bootstrap ; make ; sudo make install

I used to build Carbon Emacs up till a couple of months ago, and do
not recall this behaviour.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]