From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Setting gdb to use eshell buffer
Date: Sat, 31 Jan 2004 21:15:49 +0100 [thread overview]
Message-ID: <87ad43swlm.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 87oessm88h.fsf@pculi.herbst.fam
Ulrich Herbst <ulrich.herbst@gmx.de> writes:
> No, i haven't other ideas (and i don't understand the rest of that
> post).
A pity. I'm always looking for other ideas. Tramp needs to solve
nontrivial problems, IMHO.
> Would it be possible to use that "extended" tramp to debug perlscripts
> remote ? (I need that).
It would be the first step (of perhaps five or so) to allow you to
debug perl scripts remotely.
Kai
next prev parent reply other threads:[~2004-01-31 20:15 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 [this message]
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
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=87ad43swlm.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).