From: "T.V Raman" <raman@google.com>
To: Richard Stallman <rms@gnu.org>
Cc: qhong@mit.edu, theophilusx@gmail.com, eggert@cs.ucla.edu,
emacs-devel@gnu.org
Subject: Re: About implementing libre.js/el in Emacs
Date: Mon, 31 Aug 2020 06:48:25 -0700 [thread overview]
Message-ID: <p9136436i52.fsf@google.com> (raw)
In-Reply-To: <E1kCasv-0004Xo-Ge@fencepost.gnu.org> (Richard Stallman's message of "Sun, 30 Aug 2020 23:53:33 -0400")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1337 bytes --]
Richard Stallman <rms@gnu.org> writes:
I was thinking more of manipulating DOM (Document Object Model)
structures via elisp code rther than JS> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > At the same time, having a "web in emacs extension language" might
> > allow us to imagine, invent, and create a whole new class of
> > collaborative interactions
>
> That phrase is evocative, but it isn't concrete. It could mean many
> things. To me, it suggests the idea of a web site that people
> interact with through a particular Emacs Lisp program. Is that what
> you mean?
>
> If a web site intends users to run some specific Emacs Lisp program,
> the way to do this and respect the users' freedom is to release
> that program like any other free software package. That way, users
> can make and use modified versions. Users and distros can release
> and maintain their versions, too.
>
> But I don't see that this has anything to do with the question
> of Emacs and Javascript. Javascript plays no role in it.
>
> If you mean something else, could you describe it more clearly?
--
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2020-08-31 13:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 19:14 About implementing libre.js/el in Emacs Qiantan Hong
2020-08-29 21:10 ` Paul Eggert
2020-08-30 2:26 ` Tim Cross
2020-08-30 2:45 ` Qiantan Hong
2020-08-30 7:44 ` Tim Cross
2020-08-30 14:13 ` T.V Raman
2020-08-31 3:53 ` Richard Stallman
2020-08-31 4:11 ` Qiantan Hong
2020-08-31 4:15 ` Stefan Monnier
2020-08-31 4:17 ` Qiantan Hong
2020-08-31 13:48 ` T.V Raman [this message]
2020-09-01 3:22 ` Richard Stallman
2020-08-31 3:57 ` Richard Stallman
2020-08-31 3:57 ` Richard Stallman
2020-08-31 4:13 ` Qiantan Hong
2020-09-01 3:24 ` Richard Stallman
2020-08-31 4:24 ` Qiantan Hong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p9136436i52.fsf@google.com \
--to=raman@google.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=qhong@mit.edu \
--cc=rms@gnu.org \
--cc=theophilusx@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).