[Top][All Lists]

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

Re: [Bug-zile] curses.tigetstr("kbs") vs ^H again :(

From: Gary V. Vaughan
Subject: Re: [Bug-zile] curses.tigetstr("kbs") vs ^H again :(
Date: Sat, 15 Sep 2012 11:39:39 +0700

Hi Reuben,

On 15 Sep 2012, at 03:15, Reuben Thomas <address@hidden> wrote:

> On 14 September 2012 04:20, Gary V. Vaughan <address@hidden> wrote:
>> Since your Tue Sep 11 23:31:07 2012 +0100 commit 2fd0fc7:
>> Removing the kbs entry from the keycode table constructor again fixes it for 
>> me,
>> but I guess from your commit message that you need it on your terminal for
>> BACKSPACE to work correctly?
> Yes.

Yuck :(

> I am losing the will to care about this issue, but before you push
> your patch, would you mind re-reading the discussion we had about this
> last year? The outcome was that the latest Mac OS X Terminal shipped
> with xterm-256color as the default terminal setting, and that
> everything worked fine there.


> Again, can we establish whether the problem is in the terminfo
> database, in which case that should be fixed rather than Zile, or in
> Zile?

But I'm now having the same problem inside screen (actually tmux, but they
both use the same TERM settings) because the screen and screen-256color
terminfo databases have kbs=^H.  I think we both agree that this is a bug,
and I'll email Thomas Dickey presently to report it, and get some feedback.

> Also, why does the test hang? Since quoted-insert calls
> getkey_unfiltered, why doesn't the code just get returned as for any
> other code?

Actually, now that you highlight it.  *That* is actually the bug I'm
tripping:  Using Lua Zile interactively works fine without my patch, in
that the backspace key does the right thing.  Although, of course, the
stupid kbs=^H setting grabs ^H before Zile can bind it to anything more
useful, so a literal ^H also behaves like a backspace keypress.  But,
there's no reason that should hang the interactive quoted-insert test :(

> The key email from you was sent on 15/08/2011.

Ack.  Thanks for the pointer.

> At the very least, I'd like to end up with documentation that reduces
> our chances of going round this loop again.

I'll email Thomas Dickey, and try to root out the test suite hanging
bug (out of interest, does make check in current HEAD lua running inside
screen hang for you too?).

Would you mind writing a first cut at the documentation you want to add?

Gary V. Vaughan (gary AT gnu DOT org)

reply via email to

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