Hello Johan,
On Saturday, January 26, 2008 at 15:31:14 +0100, Johan Svedberg wrote:
> keybindings in vim using Ctrl and Meta with the Left and Right arrow
> keys [...] works fine outside of screen but not from within.
Those key combinations are not very portable across terminals. They
are n
Hello Phil,
On Tuesday, January 22, 2008 at 9:09:39 -0500, Phillip Michael Gregory wrote:
> PuTTY sends the same escape sequences as (IIRC) the linux console for
> F1-F4 by default. This is a problem because it sets its $TERM to
> 'xterm' which on many systems has different F1-F4 escape sequence
Hello Trent,
On Saturday, January 26, 2008 at 10:43:17 +1100, Trent W. Buck wrote:
> Here are some notes I made on the subject a few years ago.
Nice document, bravo! I'll comment a couple details about the
screen-256color terminfo entry:
> ccc,
>
> initc=\E]4;%p1%d;rgb\:%p2%{2
Hello Christian,
On Tuesday, June 19, 2007 at 8:09:48 +0200, Christian Andersson wrote:
> When i press lshift+rarrow i only get some output data instead of
> moving the cursor (in mcedit) for example.
Shift-arrows are not part of the Screen virtual terminal. Those keys
are not translated be
On Wednesday, April 25, 2007 at 15:21:38 +0200, Nikolai Weibull wrote:
> the setaf/setab alternatives that are used now look very complex.
Yes, they minimize bytes transmitted on the wire, but don't minimize
their own unreadability... ;-) The principle is to send the shorter old
color sequen
On Monday, April 23, 2007 at 21:56:59 +0200, Nikolai Weibull wrote:
> On 4/23/07, Alain Bench <[EMAIL PROTECTED]> wrote:
>> An enhanced version of your [screen-256color] entry is included in
>> the official terminfo database
> "Enhanced"? ;-)
Slightly ric
Hello Nikolai,
On Saturday, April 21, 2007 at 16:25:13 +0200, Nikolai Weibull wrote:
> I've posted a suggestion for a screen-256color terminfo entry, but
> I don't think it's been picked up for the distribution, yet.
An enhanced version of your entry is included in the official
terminfo dat
On Thursday, May 25, 2006 at 17:16:44 +0100, Stéphane Chazelas wrote:
> On Fri, May 19, 2006 at 01:55:59PM +0200, Alain Bench wrote:
>> named yet longer "screen-256color.xterm-256color"...
> Well, screen.xterm-256color lets screen select it automatically.
Select
Bonjour Stéphane,
On Tuesday, May 9, 2006 at 8:05:43 +0100, Stéphane Chazelas wrote:
> Here is what I have. This is screen entry with some xterm specific
> keys and features added (note that the name "screen.xterm-256color" is
> too big for some curses implementations).
And given it provide
On Monday, May 15, 2006 at 12:54:37 +0200, Michael Schroeder wrote:
> On Sat, May 13, 2006 at 03:27:24PM +0200, Alain Bench wrote:
>> the [backspace] key doesn't seem to be so translated. Why?
> Basically because "kbs" tends to be wrong.
Thank you for the explan
On Monday, May 15, 2006 at 11:02:47 -0400, Aaron Davies wrote:
> [PuTTY's] TERM is xterm by default
I know: It's available virtually everywhere, but is suboptimal. If
all hosts you connect to have a recent enough "putty" entry in their
terminfo database, or even a "putty-256color" one, it wo
Hello Michael,
On Saturday, May 13, 2006 at 1:03:47 +0200, Michael Schroeder wrote:
> Actually I don't know a single application that looks at kbs.
Mutt: To be able to bind the key to a function, kbs has
to be right. Example try "bind index show-version" and press
the key: It shouts eithe
On Thursday, May 11, 2006 at 11:44:24 -0400, Aaron Davies wrote:
> On 5/11/06, Alain Bench <[EMAIL PROTECTED]> wrote:
>>| $ infocmp -1 | grep kbs
>>| kbs=^H,
> Nope, I get \177
Good. It's the good kbs value, describing PuTTY's default config
Terminal
Hello Aaron,
On Wednesday, May 10, 2006 at 14:56:27 -0400, Aaron Davies wrote:
> Backspace works fine in the shell running inside screen (bash), but
> not at all in most other contexts
Directly in PuTTY *outside* of Screen, check:
| $ infocmp -1 | grep kbs
| kbs=^H,
| $ TERM=putty in
Hello Ed,
On Monday, April 10, 2006 at 23:37:07 -0400, Edward Dench wrote:
> I have not been able to reproduce
>| echo -ne "\e[?1000H" #turn mouse reporting on
That should be a lower case 'h', and echo -e "\e" behaviour is not
constant across various shells and /bin/echos. If you had GNU pr
Hello Michael,
On Tuesday, March 28, 2006 at 13:02:13 +0200, Michael Schroeder wrote:
> I think this is a bug, screen should not use the xterm compatibility
> hack if the "colors" terminfo entry is greater than 8.
Understood and agreed: Screen should then not send at all the "dark"
code, bu
Hello,
I have a problem to display colors #8 to #15 in Screen 4.0.2 on a
PuTTY 0.58 terminal. What gets displayed is color number minus 8: The
dark colors #0 to #7.
Example: In PuTTY I export TERM=putty-256color, and have added such
a customized entry to my system terminfo database from
N
17 matches
Mail list logo
