From: Joe Corneli <jcorneli@math.utexas.edu>
Subject: Re: making contents of other programs transparent to Emacs
Date: Mon, 16 Aug 2004 18:22:15 -0500 [thread overview]
Message-ID: <E1Bwqnv-0007ij-00@linux183.ma.utexas.edu> (raw)
> I had more of the idea of interactively editing the contents of
> other programs.
M-x shell M-x term
Term is in my experience way too slow to be useful for running
e.g. Lynx. And the above suggestion is of less than dubious utility
for working with programs like Mozilla.
I was not clear about the full mileage I would like to get out of
the idea I'm talking about here.
The general idea is to use Emacs as a "development platform" in a
sense similar to that in which Gnome is a development platform --
but to draw on all the strengths of Emacs. Specifically, I would
like
* to be able to select text from any window using familiar Emacs
editing commands
* to be able to search for a string across all open X windows
* to be able to fully script window selection routines and
keyboard commands to non-Emacs windows
I'm not saying that this would be possible to do with existing
tools, because I don't think it is. I'm looking for feedback about
the steps that would be needed to make these things possible.
next reply other threads:[~2004-08-16 23:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 23:22 Joe Corneli [this message]
2004-08-28 14:40 ` making contents of other programs transparent to Emacs Kai Grossjohann
[not found] <mailman.537.1093715759.1998.help-gnu-emacs@gnu.org>
2004-08-30 6:44 ` Mathias Dahl
-- strict thread matches above, loose matches on Subject: below --
2004-08-28 17:50 Joe Corneli
[not found] <38r1iv$3r7l6i@ironman3.mail.utexas.edu>
2004-08-16 17:03 ` Joe Corneli
[not found] ` <mailman.1442.1092676134.2011.help-gnu-emacs@gnu.org>
2004-08-16 17:48 ` Kevin Rodgers
[not found] <mailman.813.1092235424.2011.help-gnu-emacs@gnu.org>
2004-08-12 2:29 ` Barry Margolin
2004-08-12 9:59 ` Bruce Ingalls
2004-08-11 14:39 Joe Corneli
2004-08-11 21:27 ` Milan Zamazal
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Bwqnv-0007ij-00@linux183.ma.utexas.edu \
--to=jcorneli@math.utexas.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.