From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Network connection: 99% CPU
Date: Fri, 25 Aug 2006 00:45:24 +0200 [thread overview]
Message-ID: <44EE2C04.9080101@student.lu.se> (raw)
In-Reply-To: <m3sljlriv2.fsf@kfs-l.imdomain.dk>
Kim F. Storm wrote:
> I fixed a problem related to server sockets on W32.
>
Do you mean that emacsclient/server now works on w32? Did I really miss
that event ...
next prev parent reply other threads:[~2006-08-24 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 15:55 Network connection: 99% CPU dhruva
2006-08-24 20:14 ` Kim F. Storm
2006-08-24 22:45 ` Lennart Borgman [this message]
2006-08-24 22:59 ` Jason Rumney
[not found] ` <f7ccd24b0608241638t48415f87q2ca5166de587e966@mail.gmail.com>
2006-08-24 23:40 ` Juanma Barranquero
2006-08-25 1:39 ` Eli Zaretskii
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=44EE2C04.9080101@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).