From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Nic Ferrier Newsgroups: gmane.emacs.devel Subject: Re: A new online publishing tool for Texinfo documents. Date: 24 Nov 2003 16:39:39 +0000 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <8765h9d8l0.fsf@kanga.tapsellferrier.co.uk> References: <87r800dr09.fsf@kanga.tapsellferrier.co.uk> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1069692167 13478 80.91.224.253 (24 Nov 2003 16:42:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Nov 2003 16:42:47 +0000 (UTC) Cc: epameinondas@gmx.de, bob@rattlesnake.com, emacs-devel@gnu.org, juri@jurta.org, karl@freefriends.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Nov 24 17:42:43 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AOJnP-0005bj-00 for ; Mon, 24 Nov 2003 17:42:43 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AOJnP-0004M5-00 for ; Mon, 24 Nov 2003 17:42:43 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AOKkf-0000oV-6p for emacs-devel@quimby.gnus.org; Mon, 24 Nov 2003 12:43:57 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AOKjG-0000BF-R6 for emacs-devel@gnu.org; Mon, 24 Nov 2003 12:42:30 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AOKiY-0008IC-Rf for emacs-devel@gnu.org; Mon, 24 Nov 2003 12:42:17 -0500 Original-Received: from [217.34.135.17] (helo=tf1.tapsellferrier.co.uk) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AOKiY-0008HQ-6B; Mon, 24 Nov 2003 12:41:46 -0500 Original-Received: from [194.74.202.254] (helo=kanga.tapsellferrier.co.uk) by tf1.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 1AOJlA-0002rV-00; Mon, 24 Nov 2003 16:40:24 +0000 Original-Received: from localhost ([127.0.0.1] helo=kanga.tapsellferrier.co.uk ident=nferrier) by kanga.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 1AOJkS-0005hi-00; Mon, 24 Nov 2003 16:39:40 +0000 Original-To: rms@gnu.org In-Reply-To: Original-Lines: 33 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18089 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18089 Richard Stallman writes: > I'm unsure about Lynx but for Emacs/W3 I'm sure we could add a hack > so that we could use Elisp as an in-page language. > > Perhaps each instruction could be provided both in Javascript and in > Emacs Lisp; then each program to display the file could use whichever > one is easier. Yes, that was what I was suggesting. The trouble with doing that is that viruses become a real possibility. We'd have to invent some security checking stuff to ensure that elisp programs embedded in webpages only did what they were allowed to do. Of course, with elisp that's not as difficult as it is in other languages because an elisp parser is not as difficult to write... but it's still more work than linking in Javascript. It also only solves the problem for this application. More and more websites are using Javascript in the page. > Or if the Javascript that you need is very limited and stereotyped, > a simple Lisp program could recognize the standard Javascript programs > with regexps, and handle each case appropriately. That's a good idea. We could tag the javascript with comments so that they could be recognised easily. Nic