wcmd unusable when DISPLAY not set. Again.

[Dan Kegel]

It's been a year or so since my last complaint, time
to complain again!

wcmd is currently unusable when DISPLAY is not set.

Normally, you can do
  programs/wcmd/wcmd
and get a nice DOS prompt.  However, if you do
  unset DISPLAY
  programs/wcmd/wcmd
you get a nonfunctional DOS prompt; for each keystroke,
it gives you a new prompt.   Pressing ^C terminates wine,
and leaves stdin in raw mode.  This makes it really friggin' hard to
use batch files
in a cron job or any other situation where you don't have X
available.  (And *please* don't tell me to set up a fake X server
for this; that should simply not be needed. )

I get pissed off about this every time I run into it, and
I'm getting tired of having to figure this out over and over
again.  Grr, grr, grr.  Maybe I should figure out how to make
a regression test for this so the next time somebody breaks
it, I'm not the first person to notice.

[Alexandre Julliard]

Dan Kegel  writes:
> It's been a year or so since my last complaint, time
> to complain again!
>
> wcmd is currently unusable when DISPLAY is not set.
>
> Normally, you can do
>   programs/wcmd/wcmd
> and get a nice DOS prompt.  However, if you do
>   unset DISPLAY
>   programs/wcmd/wcmd
> you get a nonfunctional DOS prompt; for each keystroke,
> it gives you a new prompt.   Pressing ^C terminates wine,
> and leaves stdin in raw mode.  This makes it really friggin' hard to
> use batch files
> in a cron job or any other situation where you don't have X
> available.  (And *please* don't tell me to set up a fake X server
> for this; that should simply not be needed. )

What we should probably do, now that we have support for a null
display driver, is to flesh this out a little more and get rid of the
tty driver. I don't think anybody in their right mind actually wants
to run graphical apps on a tty, and the null driver is probably much
closer to what people like you actually need.

[Saulius Krasuckas]

* On Mon, 3 Oct 2005, Alexandre Julliard wrote:
> What we should probably do, now that we have support for a null
> display driver, is to flesh this out a little more and get rid of the
> tty driver.

Alexandre, you mean to eliminate tty driver from the tree at all?
> I don't think anybody in their right mind actually wants to run 
> graphical apps on a tty, and the null driver is probably much closer to 
> what people like you actually need.

Hmmm, I am the one with a non-right mind, who wants to run Microsoft Word 
with a look'n'feel of TurboVision (well, NCURSES would suffice too) and to 
play Diablo1 using AA-lib.  I am serious, really. :-)

So I think we just should switch defaults to a nulldrv, but let the ttydrv 
lives here and waits for a better times.  Please.

Thanks. :-)

[Alexandre Julliard]

Saulius Krasuckas  writes:
> Hmmm, I am the one with a non-right mind, who wants to run Microsoft Word 
> with a look'n'feel of TurboVision (well, NCURSES would suffice too) and to 
> play Diablo1 using AA-lib.  I am serious, really. :-)
>
> So I think we just should switch defaults to a nulldrv, but let the ttydrv 
> lives here and waits for a better times.  Please.

Why?  It's really an empty skeleton at this point, all it does is mess
up the screen and dump a lot of FIXMEs, and I doubt it will ever do
more than that. Putting it out of its misery seems the right thing to
do.

[Saulius Krasuckas]

* On Mon, 3 Oct 2005, Alexandre Julliard wrote:
> - Saulius Krasuckas  writes:
> > So I think we just should switch defaults to a nulldrv, but let the 
> > ttydrv lives here and waits for a better times.  Please.
>
> Why?  It's really an empty skeleton at this point, all it does is mess 
> up the screen and dump a lot of FIXMEs, and I doubt it will ever do more 
> than that. Putting it out of its misery seems the right thing to do.

Ok then.  My impression was, some thousands of code lines will be removed.

[Detlef Riekenberg]

Am Montag, den 03.10.2005, 17:40 +0200 schrieb Alexandre Julliard:
> > So I think we just should switch defaults to a nulldrv, but let the ttydrv 
> > lives here and waits for a better times.  Please.
>
> Why?  It's really an empty skeleton at this point, all it does is mess
> up the screen and dump a lot of FIXMEs, and I doubt it will ever do
> more than that.

Windows has a printer-Driver (tty.drv, tty.dll and other Files) for
Charactermode-Printing

Throwing away dlls/ttydrv or move that to dlls/winetty give us room for
that printer-driver.