Re: gdb-ui almosts works in NT

[Nick Roberts <nick@nick.uklinux.net>]

 > >> 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.
 > > 
 > > I don't understand why is this important; perhaps someone else does.

I don't know if its important but it gives the user features like accessing
previous input (C-p) and to send signals to the inferior (although this can
probably be done from the GUD buffer).

 > FYI, IELM had a similar problem, which has been fixed like so:
 > 
 >     ;; Was cat, but on non-Unix platforms that might not exist, so
 >     ;; use hexl instead, which is part of the Emacs distribution.
 >     (condition-case nil
 > 	(start-process "ielm" (current-buffer) "hexl")
 >       (file-error (start-process "ielm" (current-buffer) "cat")))

There appear to be two problems:

1) gdb-ui doesn't output to the I/O buffer in NT.
2) cat might not exist in NT.

To solve 1) I propose to get rid of the I/O buffer in NT. Then 2) would
no longer be an issue as cat (or hexl) would not be needed in NT. To do this
(and cover Windows NT/2K/9X/ME?) what case should I consider?

(eq system-type 'windows-nt)?
(memq system-type '(ms-dos windows-nt))?
something else?

Nick