all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Bennee <kernel-hacker@bennee.com>
To: Peter Dyballa <Peter_Dyballa@web.de>
Cc: help-gnu-emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Tracking down why emacsclient -c is so slow
Date: Sat, 22 Aug 2009 13:47:52 +0100	[thread overview]
Message-ID: <b2cdc9f30908220547w686a5ca1g932a5fec697df53d@mail.gmail.com> (raw)
In-Reply-To: <F4FCF404-423B-4E02-85CC-FD6737064A11@web.de>

2009/8/22 Peter Dyballa <Peter_Dyballa@web.de>:
>
> Am 22.08.2009 um 13:33 schrieb Alex Bennee:
>
>> It's definitely something other than graphics performance. The frame
>> actually appears very quickly it just takes a while before I can start
>> editing.
>
> So it is your init file/customisation.

Apparently so, although it's unclear what in it is causing the slow
down. Adding a few (message) lines to the .emacs makes it work fine
again [1]. I suspect it's triggering a very odd bug in emacs as I
can't see what would cause the slowdown in the customisation code.


[1] http://www.bennee.com/~alex/news.php?wl_mode=more&wl_eid=1292

-- 
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk




  reply	other threads:[~2009-08-22 12:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 18:25 Tracking down why emacsclient -c is so slow Alex Bennee
2009-08-21 18:54 ` Peter Dyballa
2009-08-22  8:10   ` Alex Bennee
2009-08-22 10:35     ` Peter Dyballa
2009-08-22 11:33       ` Alex Bennee
2009-08-22 11:58         ` Peter Dyballa
2009-08-22 12:47           ` Alex Bennee [this message]
2009-08-22 14:03           ` Alex Bennee
2009-08-22 14:26             ` Alex Bennee
     [not found]   ` <mailman.5119.1250928641.2239.help-gnu-emacs@gnu.org>
2009-08-22  9:53     ` A.Politz
2009-08-22 11:27       ` Alex Bennee

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b2cdc9f30908220547w686a5ca1g932a5fec697df53d@mail.gmail.com \
    --to=kernel-hacker@bennee.com \
    --cc=Peter_Dyballa@web.de \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.