[Top][All Lists]

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

Re: Issue with (not) restoring original keypad mode on exit

From: Thomas Dickey
Subject: Re: Issue with (not) restoring original keypad mode on exit
Date: Tue, 28 Oct 2014 05:32:53 -0400
User-agent: Mutt/1.5.20 (2009-06-14)

On Tue, Oct 28, 2014 at 10:18:09AM +0300, Paul Fertser wrote:
> Hello,
> I'm sorry to nag, but can please someone answer this question? I'm

It's a matter of user (and application) expectations, e.g., for the multitude
of users (particularly of bash) who rely upon hardcoded behavior.

> already using a solution that seems acceptable and works well for me,
> but I'm worried about the others (probably it's not actually an issue
> though, as I haven't managed to find any similar complaints on the web
> yet), and additionally my curiousity keeps itching me.
> On Mon, Oct 06, 2014 at 11:44:36AM +0400, Paul Fertser wrote:
> > what is the reasoning of using "keypad mode" ever on terminals that
> > lack not only keypad but even a keyboard altogether? I've tried
> > commenting out smkx and rmkx in "screen" definition along with
> > changing k* variables to match linux-basic and so far couldn't

The "linux" entry doesn't have smkx/rmkx, so it's unlikely you could see
a difference - at best(*), "screen" only inherits capabilities declared in
the actual terminal.

(*) in practice, screen's color- and function-key behavior doesn't really
    hide much of the actual terminal.

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

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