[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-readline] nul's from tputs(called by rl_ding) when prefer_visib

From: Chet Ramey
Subject: Re: [Bug-readline] nul's from tputs(called by rl_ding) when prefer_visible_bell is On
Date: Sat, 01 May 2010 13:51:58 -0400
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1

On 4/30/10 10:19 AM, McConnaughey, Bill wrote:

> You can test this fairly easily.  Run gdb on your program (from another
> terminal using `attach', if necessary), set a breakpoint in rl_ding,
> wait for it to hit, and examine the value of _rl_visible_bell.  If it
> doesn't include 853 NUL characters, the problem must be tputs padding
> the output.
> Chet
> ---------------------------------
> Thanks for the hint, Chet. I tried it and got
> (gdb) p _rl_visible_bell
> $1= 0xb7e00637 "\33[?5h\33[?5l$<200/>"
> which is completely consistent with the record from my modified readline. I 
> made a guess and changed the '$' (_rl_visible_bell[10]) to nul. Then the 
> terminal blinked in the same manner as before, but the 853 nul's were not 
> emitted. So I still don't know where the bug is (or whether it is deliberate 
> padding), but I can easily patch it.

Interesting.  My systems running xterm terminate the value after the
"5l".  I tested on Mac OS X and Ubuntu; RHEL xterm, interestingly, doesn't
appear to supply a visible bell string.  What are you using?

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]