unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "T.V Raman" <raman@google.com>
Cc: qhong@mit.edu, theophilusx@gmail.com, emacs-devel@gnu.org,
	eggert@cs.ucla.edu
Subject: Re: About implementing libre.js/el in Emacs
Date: Sun, 30 Aug 2020 23:53:33 -0400	[thread overview]
Message-ID: <E1kCasv-0004Xo-Ge@fencepost.gnu.org> (raw)
In-Reply-To: <p91imd01att.fsf@google.com> (raman@google.com)

[[[ 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?

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2020-08-31  3:53 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 [this message]
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
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=E1kCasv-0004Xo-Ge@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=qhong@mit.edu \
    --cc=raman@google.com \
    --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).