From:	broeker AT physik DOT rwth-aachen DOT de
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: scrolling shell output
Date:	29 Mar 2000 13:06:26 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	26
Message-ID:	<8bsv4i$jja$1@nets3.rz.RWTH-Aachen.DE>
References:	<8bs95q$g3$1 AT nnrp1 DOT deja DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 954335186 20074 137.226.32.75 (29 Mar 2000 13:06:26 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	29 Mar 2000 13:06:26 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Mongke <tharkad AT my-deja DOT com> wrote:

> I'm wondering whether there is any way to scroll the output from bash,
> other than using less, i.e to obtain the effect of the scrollbar in
> xterm. 

I doubt there is. DJGPP Bash uses direct hardware access, AFAIK,
i.e. its whole method of output it 100% different from the Unix-like
'terminal' interface. That's the same reason that already keeps
Windows NT from scrolling DJGPP Bash's text output. It's also one of
the main reasons why DJGPP Bash's text output is a whole lot faster
than Cygwin's one.

For other programs to be able to capture and scroll its output, you
need a Bash port like Cygwin's, which uses a simulated 'terminal'
(i.e., ANSI.SYS-style output, and an inboard ANSI.SYS-like driver) to
access colored text and cursor movement. At the very minimum, you'll
have to 'set TERM=xterm' or similar, before starting Bash, and have a
Bash that resects that setting.

OTOH, the problems you talked about with using Cygwin's rxvt seem to
stem elsewhere. Those bash sessions weren't being properly initialized
(missing $HOME, no /etc/profile, and such...), to begin with.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -