Buffered output on Windows

ruby-talk
21

“MikkelFJ” mikkelfj-anti-spam@bigfoot.com writes:

If you happen to be using command.exe switch to cmd.exe - it’s significantly
better for what it’s worth.

There was a windows port of zsh, but I’m afraid it is not up to date. I gave
up on it, but perhaps things have improved. At least unxutils has a lot of
good stuff.

Don’t forget tcsh. Works quite well on Win32. I have used it as my
regular “shell” on NT for several years.

Better than cmd.exe in several ways:

 - good command line editing (Emacs bindings)
 - good command/argument completion (customizable too)
 - dynamic abbreviations (from the history of entered commands)
 - incremental search (in the history of entered commands)
 - ...

/Johan Holmberg

22

So, I was wondering what terminals people recommend? (As was stated earlier
in this thread, rxvt seems to give me problems from time to time.)

Ah well, that’s different story. I wasn’t sure what to think of the
replies you had gotten.

I personally use Eterm, I know another one people really like a lot is
aterm. You might want to check both of those out.

db

23

“Chris Pine” nemo@hellotree.com writes:

I have run bash in cmd.com and in rxvt, […]

I find this way of expressing things confusing.

A “console application” on Win32 gets a “console” from the operating
system (if it is not started from another console application that
already has a console).

So programs like “cmd.exe”, “bash.exe” and “tcsh.exe” doesn’t need to
“run in cmd.exe”; they get a console from the OS when started.

(I don’t know anything about “rxvt” for Win32; it would be interesting
if someone could explain what that is (in Windows-terms))

/Johan Holmberg

24

But the cygwin shells are just shells - they still use cmd.exe as the
actual terminal.

martin

···

Gavin Sinclair gsinclair@soyabean.com.au wrote:

From: “MikkelFJ” mikkelfj-anti-spam@bigfoot.com

There was a windows port of zsh, but I’m afraid it is not up to date. I gave
up on it, but perhaps things have improved. At least unxutils has a lot of
good stuff.

The Cygwin port of zsh should be perfect. I tried it, was happy, but
ultimately didn’t put enough effort in. So I’m back with bash.

25

Except, of course, that it’s tcsh and not ksh or anything nice like
that (:

I far prefer ksh and ksh clones over tcsh.

-austin
– Austin Ziegler, austin@halostatue.ca on 2002.12.08 at 21.04.38

···

On Mon, 9 Dec 2002 02:35:55 +0900, Johan Holmberg wrote:

“MikkelFJ” mikkelfj-anti-spam@bigfoot.com writes:

If you happen to be using command.exe switch to cmd.exe - it’s
significantly better for what it’s worth.
There was a windows port of zsh, but I’m afraid it is not up to
date. I gave up on it, but perhaps things have improved. At least
unxutils has a lot of good stuff.
Don’t forget tcsh. Works quite well on Win32. I have used it as my
regular “shell” on NT for several years.

Better than cmd.exe in several ways:

  • good command line editing (Emacs bindings)
  • good command/argument completion (customizable too)
  • dynamic abbreviations (from the history of entered commands)
  • incremental search (in the history of entered commands)
  • …
26

“Chris Pine” nemo@hellotree.com writes:

I have run bash in cmd.com and in rxvt, […]

I find this way of expressing things confusing.

···

----- Original Message -----

I don’t think anyone runs cmd.exe in an alternative console/terminal, but…

Perhaps you’ll find this less confusing: Let’s say I have two icons on my
desktop. The targets for them are:

C:\cygwin\bin\bash.exe --login -i

C:\cygwin\bin\rxvt.exe -sr -tn xterm -e /usr/bin/bash --login -i

If I click the first, I get a generic windows console. I don’t like it.

If I click the second, I get a better
console/terminal/whatever-you-want-to-call-it, but it still has problems.

I like bash, and plan on continuing to use bash. I was just wondering if
anyone uses a better console/terminal program for windows that they would
recommend.

FWIW, I have found a third option, but it requires that I have an xserver
running on my windows machine, which I don’t always bother to do:

C:\cygwin\bin\runbash.exe --login -i -c “xterm -display :0; logout”

runbash.exe simply runs bash, but NOT in a console (nor in a window… just
“in the background”). bash then starts xterm (the cygwin port).

Chris