From: Alex Bennee <kernel-hacker@bennee.com>
To: help-gnu-emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Tracking down why emacsclient -c is so slow
Date: Fri, 21 Aug 2009 19:25:29 +0100 [thread overview]
Message-ID: <b2cdc9f30908211125h4f4f02aeg7a1f50af66a76e6a@mail.gmail.com> (raw)
On one of my machines there is a massive pause between a new frame
appearing and being able to edit the file. I'm wondering if there is
anything I can do to track down the slow bit.
I've added some (message)'s to two hooks to try and track it down. You
can see an example emacsclient -t gives:
after-make-frame-functions at Fri Aug 21 19:18:59 2009
server-visit-hook at Fri Aug 21 19:18:59 2009
When done with a buffer, type C-x #
However editing the same file with -c gives:
after-make-frame-functions at Fri Aug 21 19:18:21 2009
server-visit-hook at Fri Aug 21 19:18:25 2009
(No files need saving)
In fact this very message is being edited in a -c frame and shows a
fairly consistent 4 second delay:
after-make-frame-functions at Fri Aug 21 19:21:44 2009
enabling long lines for itsalltext [2 times]
server-visit-hook at Fri Aug 21 19:21:48 2009
When done with a buffer, type C-x #
Are there any other hooks run between after-make-frame-functions and
server-visit-hook I can hook to to see why it takes so long?
--
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk
next reply other threads:[~2009-08-21 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 18:25 Alex Bennee [this message]
2009-08-21 18:54 ` Tracking down why emacsclient -c is so slow 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
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=b2cdc9f30908211125h4f4f02aeg7a1f50af66a76e6a@mail.gmail.com \
--to=kernel-hacker@bennee.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.
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.