From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: nnimap/gssapi/imtest pty stuff
Date: 15 Feb 2001 13:45:38 +1100 [thread overview]
Message-ID: <87pugku0j1.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <dzcu25wy8nw.fsf@pandora.inf.elte.hu> (NAGY Andras's message of "15 Feb 2001 03:36:19 +0100")
On 15 Feb 2001, NAGY Andras wrote:
> NAGY Andras <nagya@inf.elte.hu> writes:
>
>> Any ideas how to fix this?
>
> setbuf(stdin, NULL) in imtest.c.
>
> I dream of a world where capabilities of emacs can be extended through
> loadable native object code and lisp wrappers, instead of having to
> parse the hairy output of helper programs, which were designed for
> debugging and not for everyday use by a mailer.
*grin* Port SSL network connection code to XEmacs as a loadable module.
21.2 support arbitrary binary extensions. :)
Daniel
--
She takes medicine medicine / Every damn day
For she thinks she is sick / She was brought up that way
-- Switchblade Symphony, _Funnel_
next prev parent reply other threads:[~2001-02-15 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 1:51 NAGY Andras
2001-02-15 2:36 ` NAGY Andras
2001-02-15 2:45 ` Daniel Pittman [this message]
2001-02-15 9:36 ` Simon Josefsson
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=87pugku0j1.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).