unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Nikolaj Schumacher <me@nschum.de>
To: Felipe Magno de Almeida <felipe.m.almeida@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs cvs (23) uses too much CPU with compilation mode
Date: Tue, 12 May 2009 13:48:31 +0200	[thread overview]
Message-ID: <6019D614-EB62-4AC6-A6FA-DC0376023481@nschum.de> (raw)
In-Reply-To: <a2b17b60905120443x5cd039eckc7d34fa842250c6a@mail.gmail.com>

On 2009-05-12, at 13:43, Felipe Magno de Almeida wrote:
> Thanks,
> I was starting to get worried my messages weren't getting through.

No, we just didn't have a clue what is going on.
(Please CC the list in your answers. I likely can't answer all your  
questions

>> Either fontification (and setting error markers) takes longer in  
>> Emacs
>> 23, or just the progress messages for fontification (because drawing
>> antialiased fonts is slower).
>>
>> Test by disabling `font-lock-mode', or setting `font-lock-verbose'  
>> to nil.
>
> It is by ssh. In console.
> I don't think (?) there's any fontification for console.

Fontification is the emacs expression for adding text properties like  
color. Even if your terminal doesn't display the color, Emacs will  
produce it in the background, because the links in the compilation  
buffer are created in the same process.





  parent reply	other threads:[~2009-05-12 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 21:28 Emacs cvs (23) uses too much CPU with compilation mode Felipe Magno de Almeida
2009-05-09  4:39 ` Felipe Magno de Almeida
2009-05-12  9:07   ` Nikolaj Schumacher
     [not found]     ` <a2b17b60905120443x5cd039eckc7d34fa842250c6a@mail.gmail.com>
2009-05-12 11:48       ` Nikolaj Schumacher [this message]
2009-05-29  1:47         ` Felipe Magno de Almeida
     [not found] ` <mailman.6869.1241843976.31690.help-gnu-emacs@gnu.org>
2009-07-02 20:38   ` daviddisco
2009-07-15 18:31     ` jvc

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=6019D614-EB62-4AC6-A6FA-DC0376023481@nschum.de \
    --to=me@nschum.de \
    --cc=felipe.m.almeida@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).