From: Oliver Heins <olli@sopos.org>
Subject: Re: emacs startup slow
Date: Sat, 09 Dec 2006 18:03:35 +0100 [thread overview]
Message-ID: <871wn980ig.fsf@sopos.org> (raw)
In-Reply-To: mailman.1691.1165679366.2155.help-gnu-emacs@gnu.org
Wolfgang Korsch <korsch@pa.uky.edu> writes:
> It turns out that it takes more than 30s for emacs to
> startup (even emacs -nw) when I run within a WEP key enabled
> network. It's fine within a network w/o WEP key (fast startup).
>
> I have no idea how to pin down the problem.
>
> Any hints or help is highly appreciated.
Does this still happen when you start emacs -q? I had a massive startup
delay due to some settings in my .emacs, which dissapeared after putting
appropriate substitutions into .Xressources.
HTH,
olli
Btw, are you related to Karl Korsch?
( http://en.wikipedia.org/wiki/Karl_Korsch )
--
Homepage: http://www.sopos.org/olli/
GnuPG-Key: http://www.sopos.org/pgp/olli.asc
GnuPG-Fingerprint: F27A BA8C 1CFB B905 65A8 2544 0F07 B675 9A00 D827
NP: Nothing
next parent reply other threads:[~2006-12-09 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1691.1165679366.2155.help-gnu-emacs@gnu.org>
2006-12-09 17:03 ` Oliver Heins [this message]
2006-12-10 0:42 ` emacs startup slow Tim X
2006-12-09 15:49 Wolfgang Korsch
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=871wn980ig.fsf@sopos.org \
--to=olli@sopos.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).