From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Setting gdb to use eshell buffer
Date: Tue, 03 Feb 2004 09:26:58 +0100 [thread overview]
Message-ID: <877jz46019.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 401ED323.9080906@yahoo.com
Kevin Rodgers <ihs_4664@yahoo.com> writes:
> Kai Grossjohann wrote:
> >
> > Or one could install a process filter that fishes things from the
> > *tramp/foo* buffer and copies them into the *compilation* buffer as
> > they arrive. But in that case, we need to prohibit users from
> > invoking Tramp in the meantime, as the *tramp/foo* buffer is already
> > busy.
>
> Isn't that necessary anyway? Because otherwise, the current
> implementation would have other Tramp data interspersed with the compile
> command's output in the *tramp/foo* buffer.
Well, my original plan was to allow multiple connections. Then each
connection could be dedicated to a single compilation, until that
compilation is finished.
If two (remote) processes are writing to the same *tramp/foo* buffer,
it is nearly impossible to tell the chunks apart later. At least I
haven't found a way to do that. But if there was a way, multiplexing
a single *tramp/foo* buffer might be the way to go.
But you're right anyway: we need a way to copy the output from the
remote end from the *tramp/foo* buffer to the *compilation* buffer, as
that output arrives, and we need to do that in the background. This
means that process filters are the easiest way. And if I want to
reuse the same *tramp/foo* buffer for multiple compilations (which is
a good idea to avoid connection setup overhead), then it won't work to
just name the buffer the *compilation* buffer...
> Would it be feasible for the Tramp compilation function to install the
> process filter and arrange for it to be uninstalled when its done?
Sure. set-process-filter will be my friend.
Kai
next prev parent reply other threads:[~2004-02-03 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.426.1069464439.399.help-gnu-emacs@gnu.org>
2003-12-17 20:17 ` Setting gdb to use eshell buffer Kai Grossjohann
2004-01-25 14:08 ` Ulrich Herbst
2004-01-31 20:15 ` Kai Grossjohann
2004-01-26 23:14 ` Kevin Rodgers
2004-01-31 20:14 ` Kai Grossjohann
2004-02-02 22:45 ` Kevin Rodgers
2004-02-03 8:26 ` Kai Grossjohann [this message]
2004-02-03 16:23 ` Stefan Monnier
2004-02-05 7:53 ` Kai Grossjohann
2003-11-22 0:24 ncohen
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=877jz46019.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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.
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).