From: Marcus Gustafsson <gaspode+news@lysator.liu.se>
Subject: Re: file-error "writing to process"
Date: Sat, 08 Jul 2006 11:35:07 +0800 [thread overview]
Message-ID: <878xn43h1w.fsf@luggage.skynet> (raw)
In-Reply-To: <mailman.3434.1151491065.9609.info-gnus-english@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
Leon <sdl.web@gmail.com> writes:
> [gnus: 5.11, emacs: 23.0.0.2 20060608]
>
> Hi there,
>
> Any body know a fix for this error:
>
> ,----
> | Debugger entered--Lisp error: (file-error "writing to process"
> | "transport endpoint is not connected" #<process idna>)
> `----
It seems Gnus failed to start the "idn" binary, if you install it you
probably will be fine.
HTH
Marcus
[-- Attachment #1.2: Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english
next parent reply other threads:[~2006-07-08 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3434.1151491065.9609.info-gnus-english@gnu.org>
2006-07-08 3:35 ` Marcus Gustafsson [this message]
2006-06-28 10:37 Leon
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=878xn43h1w.fsf@luggage.skynet \
--to=gaspode+news@lysator.liu.se \
/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 NNTP newsgroup(s).