Re: screen discards undefined escape sequences
Dan Nelson <[email protected]>
| Newsgroups | gmane.comp.gnu.screen |
|---|---|
| Message-ID | <[email protected]> |
In the last episode (Jan 19), Mark Plaksin said: > Will you not patch screen because you know that dropping unknown > escape sequences is the correct behavior? If so I'll encourage the > Emacs folks to pick something else to key on. > > Is screen the only program doing it right? Everything else I've > tried (bash, xterm, etc) passes the unknown escapes through. Well, bash isn't a terminal emulator, so it doesn't process ANSI escapes at all. xterm on my system eats unknown escapes: $ printf "\033AnSiT\n" nSiT $ xterm -v XFree86 4.2.99.903(174) $ I'm not sure how you are seeing this in any case. If you're running screen, then emacs, then starting term-mode, screen shouldn't ever see those escapes. Same for running emacs in an xterm. Are you running emacs, starting term-mode, then running screen inside that, then opening up multiple windows? -- Dan Nelson [email protected] Yahoo! Groups Links To visit your group on the web, go to: http://groups.yahoo.com/group/gnu-screen/ To unsubscribe from this group, send an email to: [email protected] Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/