From: Dan Christensen <jdc@jhu.edu>
Subject: Re: nnhtml type backends -- idea
Date: Wed, 19 Apr 2000 19:44:50 -0400 [thread overview]
Message-ID: <87bt351wr1.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "20 Apr 2000 01:36:51 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> That would be nice, but wouldn't the parsing rules really have to be
> elisp code? And do you really want to download possibly harmful code
> automatically?
I download gnus automatically, and that code isn't, umm, er, never mind.
:-)
Dan
--
Dan Christensen
jdc@math.jhu.edu
next prev parent reply other threads:[~2000-04-19 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-18 13:55 Kai Großjohann
2000-04-18 16:57 ` Shenghuo ZHU
2000-04-19 13:37 ` Jaap-Henk Hoepman
2000-04-20 12:49 ` Eric Marsden
2000-04-20 18:28 ` Lars Magne Ingebrigtsen
2000-04-19 23:36 ` Lars Magne Ingebrigtsen
2000-04-19 23:44 ` Dan Christensen [this message]
2000-04-20 6:46 ` Kai Großjohann
2000-04-20 18:28 ` Lars Magne Ingebrigtsen
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=87bt351wr1.fsf@chow.mat.jhu.edu \
--to=jdc@jhu.edu \
/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).