From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Richard Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Encryption code is ok
Date: Wed, 05 May 2004 16:21:05 -0400
Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Message-ID: <E1BLSt7-00050r-EC@fencepost.gnu.org>
References: <E1BL6CW-0003Ge-8y@fencepost.gnu.org>
	<x5wu3r4yk4.fsf@lola.goethe.zz>
Reply-To: rms@gnu.org
NNTP-Posting-Host: deer.gmane.org
X-Trace: sea.gmane.org 1083789736 21324 80.91.224.253 (5 May 2004 20:42:16 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Wed, 5 May 2004 20:42:16 +0000 (UTC)
Cc: emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed May 05 22:42:01 2004
Return-path: <emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 1BLTDM-0001Bx-00
	for <emacs-devel@deer.gmane.org>; Wed, 05 May 2004 22:42:00 +0200
Original-Received: from monty-python.gnu.org ([199.232.76.173])
	by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian))
	id 1BLTDM-0003j0-00
	for <emacs-devel@quimby.gnus.org>; Wed, 05 May 2004 22:42:00 +0200
Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.30)
	id 1BLTCM-00010f-Ep
	for emacs-devel@quimby.gnus.org; Wed, 05 May 2004 16:40:58 -0400
Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1BLSwl-0003Y1-Eo
	for emacs-devel@gnu.org; Wed, 05 May 2004 16:24:51 -0400
Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1BLSwA-0003Nl-Ry
	for emacs-devel@gnu.org; Wed, 05 May 2004 16:24:46 -0400
Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1BLSt8-00026F-Td
	for emacs-devel@gnu.org; Wed, 05 May 2004 16:21:06 -0400
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.24)
	id 1BLSt7-00050r-EC; Wed, 05 May 2004 16:21:05 -0400
Original-To: David Kastrup <dak@gnu.org>
In-reply-to: <x5wu3r4yk4.fsf@lola.goethe.zz> (message from David Kastrup on 05
	May 2004 00:28:27 +0200)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Xref: main.gmane.org gmane.emacs.devel:22805
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:22805

    Ok, not that the efficiency of Emacs Lisp would make this feasible,
    but just for the record: does your question encompass just code
    interfacing to cryptographic applications, or even cryptographic code
    itself written in Emacs Lisp?

Both.