unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs Slowdown
Date: Wed, 18 Mar 2015 16:34:54 +0000	[thread overview]
Message-ID: <87oanqe029.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <jwviody9x5u.fsf-monnier+INBOX@gnu.org> (Stefan Monnier's message of "Wed, 18 Mar 2015 10:53:25 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> When Emacs feels slow, what happens if you keep typing without waiting
>>> for Emacs's response?
>> It catches up eventually.
>
> Hmm... so providing input doesn't actually "wake it up": sometimes,
> I introduced bugs which caused Emacs to redisplay just before the next
> command rather than right after a command, which made it look like
> Emacs was terribly slow, even tho it was just that the screen update
> was happening at the wrong time.
> But It looks like your situation is not one of those.

I think not. I'm trying out with older versions of Emacs to see whether
the problem is recent.

Phil



  reply	other threads:[~2015-03-18 16:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 11:48 Emacs Slowdown Phillip Lord
2015-03-09 16:16 ` Eli Zaretskii
2015-03-09 21:50   ` Stefan Monnier
2015-03-10 12:37   ` Phillip Lord
2015-03-10 19:00     ` Eli Zaretskii
2015-03-09 21:59 ` Stefan Monnier
2015-03-10 12:39   ` Phillip Lord
2015-03-10 13:22     ` Stefan Monnier
2015-03-12 11:36 ` Phillip Lord
2015-03-16 11:41   ` Phillip Lord
2015-03-16 12:36     ` Stefan Monnier
2015-03-16 16:51       ` Phillip Lord
2015-03-18 12:23         ` Phillip Lord
2015-03-18 12:44           ` Stefan Monnier
2015-03-18 14:13             ` Phillip Lord
2015-03-18 14:53               ` Stefan Monnier
2015-03-18 16:34                 ` Phillip Lord [this message]
2015-03-18 16:32             ` Eli Zaretskii
2015-03-18 17:04               ` Phillip Lord

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=87oanqe029.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
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).