Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: <ding@gnus.org>
Subject: Re: nnimap/gssapi/imtest pty stuff
Date: Thu, 15 Feb 2001 10:36:14 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.30.0102151027380.4037-100000@slipsten.extundo.com> (raw)
In-Reply-To: <dzcu25wy8nw.fsf@pandora.inf.elte.hu>

On 15 Feb 2001, NAGY Andras wrote:

> > Any ideas how to fix this?
>
> setbuf(stdin, NULL) in imtest.c.

Nice.  Did you send patches upstream to CMU people?

> 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.

I believe there are patches for Emacs (20) to dynamically load .so's.
Elisp wrappers that load .so's implementing base64, md5, etc are
floating around. You'd still need to write imtest.so though.




      parent reply	other threads:[~2001-02-15  9:36 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
2001-02-15  9:36   ` Simon Josefsson [this message]

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=Pine.LNX.4.30.0102151027380.4037-100000@slipsten.extundo.com \
    --to=jas@extundo.com \
    --cc=ding@gnus.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 NNTP newsgroup(s).