unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: Problems with latest CVS.
Date: Mon, 16 Feb 2004 16:37:34 -0600 (CST)	[thread overview]
Message-ID: <200402162237.i1GMbYh08219@raven.dms.auburn.edu> (raw)

Does anybody else see any of this?

With the very latest CVS Emacs used to crash rather quickly after
startup after typing a bunch of keystrokes.  After reverting this
change:

   2004-02-16  Dmitry Antipov  <dmitry.antipov@mail.ru>  (tiny change)

	    * keyboard.c (prev_read): New static variable.
	    (read_avail_input): Use it to zero out only those slots in
	    buf[]
	    that were used last time we were called.

Emacs no longer seems to crash.

However, even after this revert old minibuffer messages about reading
directories keep getting redisplayed over and over again in rapid
succession, even after a subsequent quit.  An idle Emacs chews up
nearly twenty percent of CPU.

I do seem to have problems with my disk, but I do not believe that can
be the cause.  I just marked all my bad blocks bad and repaired my
file system.  Still, does anybody else see this with the very latest
CVS (less than 3 hours old)?

(emacs-version):
"GNU Emacs 21.3.50.1 (i686-pc-linux-gnu, X toolkit)\n of 2004-02-16 on swt40.swt.com"

Sincerely,

Luc.

             reply	other threads:[~2004-02-16 22:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 22:37 Luc Teirlinck [this message]
2004-02-16 22:47 ` Problems with latest CVS Luc Teirlinck
2004-02-16 22:55   ` Luc Teirlinck
2004-02-17  2:49     ` Luc Teirlinck
2004-02-17  3:31       ` Luc Teirlinck
2004-02-17  6:43       ` Eli Zaretskii
2004-02-17 16:47         ` Luc Teirlinck
2004-02-17 19:53           ` Luc Teirlinck
2004-02-18  0:08             ` Luc Teirlinck
2004-02-18  0:59               ` Luc Teirlinck
2004-02-18  1:10                 ` Luc Teirlinck
2004-02-17  1:37 ` Kim F. Storm
2004-02-17  2:05   ` Luc Teirlinck

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=200402162237.i1GMbYh08219@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    /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).