On 3/3/2011 4:19 PM, Dr. Ed Morbius wrote: > on 16:07 Thu 03 Mar, Les Mikesell (lesmikesell at gmail.com) wrote: >> On 3/3/2011 3:34 PM, Dr. Ed Morbius wrote: >>> on 13:36 Thu 03 Mar, Sean Carolan (scarolan at gmail.com) wrote: >>>> I really like gnu screen and use it everyday but there's one thing >>>> that is a bit inconvenient, and that's the odd line wrapping and >>>> terminal size issues that seem to pop up. The problem crops up when I >>>> type or paste a really long command, and then go back and try to edit >>>> it; the text starts to wrap over itself and you have no idea what you >>>> are editing. Any fixes for this? >>> >>> Is your local terminal type known to all remote systems (in termcap)? >>> >>> I find I have to re-map $TERM to some low-common standard (e.g.: xterm) >>> on many systems. Legacy Unix vendors being the most eggregious for >>> this. >> >> I tried to forget the incompatibilities in different old terminal types >> after about everything settled on xterm compatibility. Instead of >> running screen, can you run a desktop session under freenx on a server >> somewhere and run everything in terminal windows there (even ssh >> sessions that go elsewhere)? > > No xlibs on our servers. You need _a_ machine somewhere that can host a freenx session. It doesn't need to be the target of the ssh connections, just something that will mostly stay powered up if you want the session to stay active all the time. A development box or even a VM session that would work - or a desktop machine if it stays on all the time. It doesn't even have to run X on its own console. -- Les Mikesell lesmikesell at gmail.com