From: Paul Michael Reilly <pmr@pajato.com>
To: emacs-devel@gnu.org
Subject: Emacs in a Chrome Tab? (related to NaCl Support for Emacs discussion)
Date: Mon, 9 Jan 2012 15:41:09 -0500 [thread overview]
Message-ID: <CAGwjgEhXffyGNoe=ZORkreEo0QXjBgHzEkQeYpTGqa3fSPyHPQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
My curiosity peaked recently with the thread on NaCl support for Emacs.
Not having a clue what NaCl was all about, I took to Google to find out
more. And if I read it right, it is all about having a HTML/Javascript/CSS
wrapper around a C/C++ native code application running in the browser.
Very cool in its own right but simply awesome if that wrapped code happens
to be Emacs. The NaCl Support for Emacs discussion seems to be focused on
security/library (crypto) issues which tend to make my brain hurt so a new
thread seems appropriate to discuss this notion of Emacs running in a
Chrome tab. For all I know the current NaCl thread might be a totally
different NaCl thing than NativeClient.
I raised this issue last year (Emacs in the Cloud) but I don't recollect
any mention of NativeClient at that time. The notion of opening up a new
machine, installing Chrome (if it is not already installed), heading off to
the Chrome Web Store to get the latest NaCl version of Gnu Emacs, and then
using an Emacs tab to edit files/run shells/install ELPA packages is very
appealing to me.
Is anyone aware of technical "gotchas" that make this notion unrealizable
by a mere mortal in just one lifetime?
-pmr
[-- Attachment #2: Type: text/html, Size: 1301 bytes --]
next reply other threads:[~2012-01-09 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 20:41 Paul Michael Reilly [this message]
2012-01-09 21:08 ` Emacs in a Chrome Tab? (related to NaCl Support for Emacs discussion) Antoine Levitt
2012-01-09 21:56 ` Paul Michael Reilly
2012-01-09 22:42 ` chad
2012-01-10 7:11 ` Paul Michael Reilly
2012-01-09 23:26 ` Antoine Levitt
2012-01-10 7:19 ` Paul Michael Reilly
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='CAGwjgEhXffyGNoe=ZORkreEo0QXjBgHzEkQeYpTGqa3fSPyHPQ@mail.gmail.com' \
--to=pmr@pajato.com \
--cc=emacs-devel@gnu.org \
/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).