From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: chad Newsgroups: gmane.emacs.devel Subject: Re: Emacs in a Chrome Tab? (related to NaCl Support for Emacs discussion) Date: Mon, 9 Jan 2012 14:42:07 -0800 Message-ID: <054F6D14-733F-4F22-A4F2-6AF1189D13A0@gmail.com> References: <87boqc1t51.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1326148946 30120 80.91.229.12 (9 Jan 2012 22:42:26 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 9 Jan 2012 22:42:26 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Michael Reilly Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 09 23:42:22 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RkNv4-0005HO-7o for ged-emacs-devel@m.gmane.org; Mon, 09 Jan 2012 23:42:22 +0100 Original-Received: from localhost ([::1]:59600 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkNv3-00062J-Hs for ged-emacs-devel@m.gmane.org; Mon, 09 Jan 2012 17:42:21 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:46698) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkNuv-00062A-IO for emacs-devel@gnu.org; Mon, 09 Jan 2012 17:42:19 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RkNus-0004bc-CD for emacs-devel@gnu.org; Mon, 09 Jan 2012 17:42:13 -0500 Original-Received: from mail-qy0-f169.google.com ([209.85.216.169]:43009) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkNus-0004bG-9N for emacs-devel@gnu.org; Mon, 09 Jan 2012 17:42:10 -0500 Original-Received: by qcsd17 with SMTP id d17so2710287qcs.0 for ; Mon, 09 Jan 2012 14:42:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=8GRhKuWilfNMJvcn1AazrzVZ46ikETDFrBgdNMJ1w0Y=; b=PzIzunrJ8+j7excIrafbOhVXdGQtoR67TwjfGr8FY+eqpR7wICueI0BQ7vT+nUcT2D mtd49ASfv7yYYLg0A4D1Bl27d4H6ZbmJlfIOroGJIRys/1/dol72BZnpsBwcLXJtUfJu 0kCa3vPISTZrNdF+xLDszwtPjBADxvoE7dIZQ= Original-Received: by 10.229.76.202 with SMTP id d10mr6649325qck.21.1326148929194; Mon, 09 Jan 2012 14:42:09 -0800 (PST) Original-Received: from [10.0.0.174] ([12.198.236.170]) by mx.google.com with ESMTPS id hm10sm9973836qab.12.2012.01.09.14.42.07 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 Jan 2012 14:42:08 -0800 (PST) In-Reply-To: X-Mailer: Apple Mail (2.1251.1) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.216.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:147532 Archived-At: NativeClient is mostly about using the local processor to cut out server = round-trips for computations. Unfortunately for your idea, it doesn't = address the idea of the display engine; native client nexe's are = expected to use the browser's ui. There is some experimental 3D support = for nexe's via their alternative to NSAPI, but this is far enough away = from Emacs that a port would be complex. For your goals, I'd guess that = xembed (ala the xembed branch) is an easier practical path to a = prototype. This idea, like Tom Tromey's `rebase emacs on Common Lisp', Steve's = `Emacs in JavaScript', and the various Guilemacs attempts point out (yet = again) something I would not have guessed when I started with emacs ~22 = years ago: while the most technically valuable piece of Emacs (aside = from its freedom) is the extensive libraries of elisp code, the most = critical piece is actually the display engine. It's very hard to move = Emacs anywhere that the display engine won't go, and it seems to be very = hard to move the display engine. =20 *Chad P.S. This makes the herculean efforts of things like epoch, multi-tty, = and bidi all the more impressive. Thanks again to all the wonderful = emacs hackers out there.=