Tim Janik <[EMAIL PROTECTED]> writes:
> On Mon, 28 Feb 2005, Daniel Schepler wrote:
>
>> Package: beast
>> Severity: wishlist
>> Version: 0.6.2-3
>>
>> When I build beast, the configure stage outputs some escape sequences:
>>
>> checking whether i386-linux-gcc supports -fno-keep-static-consts... yes
>> ^[(B^[)0^[[?1049h^[[1;24r^[[m^O^[[4l^[[?7h^[[24;1H^[[?1049l^M^[[?1l^[>checking
>> whether i386-linux-gcc supports -fmessage-length=80... yes
>>
>> At least with konsole, this causes the terminal to update only the
>> bottom line as the rest of the compilation happens, which is pretty
>> annoying.
>
> this sounds like a bug in your konsole setup then. configure.in simply
> executes:
> #include <stdio.h>
> #include <curses.h>
> int main()
> {
> FILE *f=fopen("conftestval", "w");
> int c;
> if (!f) exit(1);
> initscr();
> c = COLS;
> endwin();
> fprintf(f, "%d\n",c);
> exit(0);
> }
> so any characters appearing are being put out by ncurses.
> that in turn uses escape sequences from the terminal description of
> your TERM environment variable which should match the capability set
> of konsole.
I just tried running xterm and cat'ing the build log to the terminal,
and the same thing happened there (konsole sets TERM=xterm). Maybe
the trigger here is that I'm running the build under pbuilder (which
redirects stdin to /dev/null) with stdout and stderr redirected to a
pipe.
--
Daniel Schepler "Please don't disillusion me. I
[EMAIL PROTECTED] haven't had breakfast yet."
-- Orson Scott Card
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
