This is the mail archive of the
mailing list for the Cygwin project.
Re: Inetd & stdout partly solved (was inetd vs. cl)
- To: Rui-Tao Dong <rdong at newport dot com>
- Subject: Re: Inetd & stdout partly solved (was inetd vs. cl)
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- Date: Mon, 12 Mar 2001 14:34:06 -0500
- CC: cygwin at cygwin dot com
- References: <v5hf16isod.fsf@P...> <v5k85u96w8.fsf@Phantom-Slow.newport.com>
Rui-Tao Dong wrote:
> I think I know what the problem is, although I haven't figure out the
> right place to fix it yet.
> I re-built XEmacs (w/ X support) and it produced a little utility
> called runemacs. If I call runemacs to start XEmacs from a telnet
> session w/ inetd running as service, all stdout gets redirected to my
> emacs buffer. If I start XEmacs directly, some stdout goes to a DOS
> window. I checked the runemacs source and found the following
> Apparently, the wShowWindow flags was set in a CYGWIN window, but not
> from inetd started as a service.
I wasn't aware that runemacs (aka run.exe) could be used for this
purpose. Cool. FWIW, "run" contains almost identical code (*) and is
available standalone from
(*) I took the runemacs code from XEmacs(21.0ish) and added lots of
stuff. Then, I *think*, my version was absorbed back into
XEmacs(21.1ish). Then the whole runemacs thing was dropped in the 21.2
series because 21.2cygwinXEmacs builds as a GUI (no console).
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple