unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Is Emacs in a usable state at the moment?
Date: Sun, 01 Dec 2013 15:52:18 +0100	[thread overview]
Message-ID: <m3pppgd3od.fsf@stories.gnus.org> (raw)
In-Reply-To: <1DC465A3-832A-449F-9118-C4511A16AE8B@swipnet.se> ("Jan \=\?iso-8859-1\?Q\?Dj\=E4rv\=22's\?\= message of "Sun, 1 Dec 2013 15:43:39 +0100")

Jan Djärv <jan.h.d@swipnet.se> writes:

> It is a work in progress, resizing windows by pixels instead of
> rows/columns, but additional debugging is welcome.

Ah, right.

> The 100% I've only seen on GnuStep, not X.  I've not seen a hang
> either, can you catch it in the debugger?

The 100% CPU usage was, I think, completely unrelated -- it was a local
issue.

The hang happened when I did the following:

`M-x debbugs-gnu' and then selected some bugs.  I entered into one of
the reports, and then did some work, and then when I exited one of the
groups, Emacs hung.  It made the "visual bell" areas go white, so
perhaps it was a bit of the error handling code that did something
wrong?

It just happened once.

> The 72 instead of 80 I've seen (but in my case, 79, 83 or 84).
>
> Which toolkit did you compile with?

Let's see...  It says:

  What toolkit should Emacs use?                          LUCID

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2013-12-01 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 14:25 Is Emacs in a usable state at the moment? Lars Magne Ingebrigtsen
2013-12-01 14:43 ` Jan Djärv
2013-12-01 14:52   ` Lars Magne Ingebrigtsen [this message]
2013-12-01 16:52     ` Stefan Monnier
2013-12-01 23:53       ` Dmitry Gutov
2013-12-02  7:38         ` martin rudalics
2013-12-01 15:47 ` Harald Hanche-Olsen
2013-12-01 16:29   ` Jan Djärv
2013-12-01 23:00 ` Richard Stallman

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=m3pppgd3od.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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).