From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org
Subject: Re: gdb-ui almosts works in NT
Date: Mon, 31 Mar 2003 22:04:00 +0100 [thread overview]
Message-ID: <16008.44352.107937.312219@nick.uklinux.net> (raw)
> > I'm trying to get gdba
> > working under NT Emacs. Almost everything works. One minor issue is
> > that gdb-ui.el is hardcoded at one point to use "/bin/cat", so I just
> > put a copy of the msys (mingw) cat.exe there.
> It's wrong for Emacs to use such code, IMHO. It should either invoke
> `cat' (and let it be found along PATH),
I agree. I'll make this change.
> or, better, implement some
> code that would eliminate the need for an external program altogether,
> since `cat' is not guaranteed to be available on every platform
> supported by Emacs.
> It strikes me that it woyldn't be hard to eliminate the need for
> `cat', since Emacs already has a means to visit files.
The output from the inferior could be sent directly to the input/output buffer
but the author of this part of the code from gdba.el (Tom Lord?) used cat
because:
;; We want to use comint because it has various nifty and familiar
;; features. We don't need a process, but comint wants one, so create
;; a dummy one.
(make-comint-in-buffer
(substring (buffer-name) 1 (- (length (buffer-name)) 1))
(current-buffer) "/bin/cat")
> > The only problem is I can't
> > get the program IO to run in the input/output window in emacs. It
> > runs always in its own DOS window.
> What compiler did you use to compile that program? Was that MinGW's
> GCC?
I downloaded Emacs for NT and MinGW for the first time today and this didn't
seem to be just a problem with gdb-ui.el. `M-x gdb' from gud.el also sent the
output from the inferior to its own DOS window. Even if `gdb mytest' is run in
a DOS window (no Emacs) then the inferior outputs to its own DOS window and
does not seem able to share the window with gdb like in GNU/Linux.
However, I have no real experience with Emacs for NT, so if you can see changes
that will make it work for this platform too, please install them.
Nick
next reply other threads:[~2003-03-31 21:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 21:04 Nick Roberts [this message]
2003-04-01 4:28 ` gdb-ui almosts works in NT Eli Zaretskii
2003-04-01 18:55 ` Edward O'Connor
2003-04-01 21:06 ` Nick Roberts
2003-04-01 21:31 ` Stefan Monnier
2003-04-02 4:12 ` Eli Zaretskii
2003-04-02 14:14 ` Stefan Monnier
2003-04-03 3:49 ` Eli Zaretskii
2003-04-03 7:55 ` Jason Rumney
2003-04-02 4:08 ` Eli Zaretskii
2003-04-02 17:28 ` Jonathan Luntz
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 17:29 Nick Roberts
2003-04-03 17:52 ` Jonathan Luntz
[not found] <3E84A28A.2090407@umich.edu>
2003-03-31 6:45 ` Eli Zaretskii
2003-03-31 15:29 ` Stefan Monnier
2003-03-31 16:38 ` Jonathan Luntz
2003-03-31 19:17 ` Eli Zaretskii
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=16008.44352.107937.312219@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--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).