From: tv.raman.tv@gmail.com (T.V Raman)
To: emacs-devel@gnu.org, emacs-devel@gnu.org
Subject: Feature change or bug - Emacs server
Date: Tue, 14 Jun 2011 01:49:20 +0900 [thread overview]
Message-ID: <4df63f95.a511440a.7545.ffffce92@mx.google.com> (raw)
Ted,
1+ on not attempting to implement what you call the pile of
undefined / open-ended Web specs in Emacs -- I say this even
though I would love to have a full-fledged browser in Emacs.
Eventually, I think we should connect emacs to Firefox and / or
Chrome over a socket -- mozrepl for Firefox did a lot of this,
but appears to have stalled. Chrome has a socket-level debugging
protocol that could be leveraged for this -- google searches
showed an early glimpse of this at github.
Tim, that may be something you might want to look at.
As someone who "already" uses Emacs as the desktop (via
Emacspeak), I definitely think emacs-panel.el could make the
Emacspeak Audio Desktop even better -- and I look forward to
it. One of the first things I would want is to mimic things like
nm-applet -- today, that's one of the few things I find
impossible to do without waving a mouse at the Gnome GUI.
--
--
next reply other threads:[~2011-06-13 16:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 16:49 T.V Raman [this message]
2011-06-13 17:11 ` Feature change or bug - Emacs server Mohsen BANAN
2011-06-13 17:18 ` Ted Zlatanov
2011-06-13 17:36 ` Michael Albinus
2011-06-13 23:45 ` Antoine Levitt
2011-06-14 0:57 ` Ted Zlatanov
2011-06-14 3:12 ` Tim Cross
2011-06-14 7:49 ` Antoine Levitt
2011-06-14 9:45 ` joakim
2011-06-14 8:22 ` Michael Albinus
2011-06-13 18:31 ` joakim
2011-06-14 3:18 ` Tim Cross
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 6:47 Tim Cross
2011-06-09 7:17 ` Tassilo Horn
2011-06-09 8:13 ` chad
2011-06-09 15:21 ` Stefan Monnier
2011-06-11 2:48 ` Tim Cross
2011-06-11 10:39 ` Ted Zlatanov
2011-06-13 2:09 ` Tim Cross
2011-06-13 15:47 ` Ted Zlatanov
2011-06-14 3:42 ` Tim Cross
2011-06-14 14:53 ` Lars Magne Ingebrigtsen
2011-06-14 15:01 ` Julien Danjou
2011-06-14 17:08 ` joakim
2011-06-14 16:17 ` Ted Zlatanov
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=4df63f95.a511440a.7545.ffffce92@mx.google.com \
--to=tv.raman.tv@gmail.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).