ports the printer
controller modes so isn't forwarding the escape sequences. According
to screen(1) you're interested in the po and pf capabilities.
Alternately you can probably hack around it using the ESC P sequence.
-sqweek
___
screen-user
ations use termcap/terminfo - vim is a
notable exception. The most important implication here is mouse
support, screen positioning/colour codes are generally binary
compatible between terminals I believe.
-sqweek
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
On 09/09/06, Henry Nelson <[EMAIL PROTECTED]> wrote:
I figured that likely was the problem. Would it be possible to re-write
the screen terminal description to allow the ansi sequences through? If
possible, would anyone know what needs to go in the terminfo source file?
screen has a couple of
On 05/07/06, Eric S. Johansson <[EMAIL PROTECTED]> wrote:
In last, how do I disable any interpretation of characters going through
screen and so I can have a completely transparent pipe to my
application. It seems that no matter what remapping I use, it always
gets in the way. it definitely get
What I'm trying to do is alter the behaviour of ^A c to create a new
shell in the same directory as the shell I'm currently in. I
understand this is different to screen's notion of the current
directory which makes things difficult...
The best I've come up with so far is 'bind "c" stuff "screen \