unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hadron <hadronquark@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs not redisplaying
Date: Fri, 23 Feb 2007 18:41:42 +0100	[thread overview]
Message-ID: <87mz34ai09.fsf@gmail.com> (raw)
In-Reply-To: mailman.27.1172250518.7795.help-gnu-emacs@gnu.org

Daniel <daniel@warum-ada.de> writes:

> Henrik Jegbjerg Hansen wrote:
>
>> Daniel <daniel@warum-ada.de> writes:
>>>> When I sit idly in Emacs (or use firefox, for example), and touch
>>>> nothing in Emacs -- messages in ERC and Jabber does not show up, and I
>>>> get no notifications of any kind, in the mode line or echo area, or
>>>> anything.  Only when I touch a key (e.g. C-f) in Emacs do they come, all
>>>> at once. 
>>> I'd like to hook myself in here, too, as I'm experiencing the same
>>> symptoms with compilation-mode on Emacs 22.0.93.1 (Linux, GTK). There
>>> might be a relation to Henrik's problem.
>>
>> Just to add: I use the same Emacs version, 22.0.93.1.
>>
>>> Output actually seems to keep appearing for a few moments after the
>>> key stroke.
>>
>> And this is the same for me too.
>
> For me, the culprit is cedet.
>
> When investigating the thing a little more (in order to come up with a
> minimal reproduction set), I found that compilation output appears
> fluently until I load "cedet-1.0pre3/common/cedet.el".
>
> Henrik, do you use cedet, too?
>
> I found a message in the emacs-pretest-bug archives
> (http://lists.gnu.org/archive/html/emacs-pretest-bug/2006-10/msg00013.html)
> that suggests installing cedet from CVS.  So I'll do just that.
>
> If it does work afterward, do you think one should still file a bug
> report, as the solution would require a non-released cedet version?
>
>

Same happens for me - and I have cedet loaded too. It jams output from
ecr and other eshell scripts I use.

      parent reply	other threads:[~2007-02-23 17:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23  3:31 Emacs not redisplaying Henrik Jegbjerg Hansen
2007-02-23 13:57 ` Daniel
2007-02-23 15:14   ` Henrik Jegbjerg Hansen
2007-02-23 17:08     ` Daniel
2007-02-23 17:30       ` Daniel
     [not found]       ` <mailman.28.1172251857.7795.help-gnu-emacs@gnu.org>
2007-02-23 18:49         ` Hadron
2007-02-23 20:05           ` Daniel
     [not found]           ` <mailman.31.1172261155.7795.help-gnu-emacs@gnu.org>
2007-02-23 20:39             ` Hadron
2007-02-23 20:58               ` Jiri Pejchal
2007-02-24 11:35                 ` Daniel
     [not found]                 ` <mailman.50.1172316912.7795.help-gnu-emacs@gnu.org>
2007-02-24 12:58                   ` Hadron
2007-02-23 19:40       ` Henrik Jegbjerg Hansen
     [not found]     ` <mailman.27.1172250518.7795.help-gnu-emacs@gnu.org>
2007-02-23 17:41       ` Hadron [this message]

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=87mz34ai09.fsf@gmail.com \
    --to=hadronquark@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).