[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Setting gdb to use eshell buffer
From: |
Kevin Rodgers |
Subject: |
Re: Setting gdb to use eshell buffer |
Date: |
Mon, 26 Jan 2004 16:14:22 -0700 |
User-agent: |
Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 |
Kai Grossjohann wrote:
ncohen@ucsd.edu writes:
Hi I'm using tramp to successfully transparently edit remote files
however I also want to compile and debug them from inside emacs.
How do I do this?
With difficulty :-/
Tramp comes with a file tramp-util.el which contains a function that
allows you to do remote compiles. It is, however, a fake, because it
doesn't show any output until the remote compile is finished. (M-x
compile RET shows you output as it is arriving.) And what's more,
Emacs is frozen while it is waiting for the compile to finish.
From that, I infer that Tramp has the connection write its output to a
local temporary file that it then inserts into a compilation buffer. If
that's the case, why can't the compilation buffer be set up with a process
that tail's the temp file as its written?
I'm thinking about extending Tramp to allow background processes. I
think that Tramp needs to open multiple connections to the remote host
to do that. (If somebody has other ideas, please speak up.) And if
you open multiple connections to a host, then password caching becomes
interesting. And password caching is potentially very dangerous.
Also, it would make sense to reuse connections, instead of opening a
new connection whenever you issue a new compile command.
I don't know. If caching passwords is so dangerous, maybe it is worth
the overhead to establish a new connection for each background command.
--
Kevin Rodgers