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?
On Thu, Mar 3, 2011 at 2:36 PM, 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?You wouldn't by any chance be using PuTTY to access the session? If so, you may need to play around with the terminal settings including the scroll type so that it displays correctly. I don't recall the specifics but a similar thing happened to me.
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. You can test $TERM compatibility in your shell login: tput -T $TERM init >/dev/null 2>&1 && echo yes || echo no In this case, you might want to conditionally assign some reasonable value on failure. Say: tput -T $TERM init >/dev/null 2>&1 || export TERM=xterm 'tset -q' is another test which can be used. -- Dr. Ed Morbius, Chief Scientist / | Robot Wrangler / Staff Psychologist | When you seek unlimited power Krell Power Systems Unlimited | Go to Krell!
On Thu, Mar 3, 2011 at 2:36 PM, 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?I've given up on screen and switched to "NX" for recoverable sessions. It works with X windows, the personal version is free for up to two simultaneous connections, and there are even hooks in CentOS not found in RHEL for the "nx" and "freenx" tools. It works *much* better than installing a $500 X server on the Windows client side, too.
On Sat, Mar 5, 2011 at 12:50 AM, Larry Vaden <vaden at texoma.net> wrote:> On Fri, Mar 4, 2011 at 6:46 PM, Nico Kadel-Garcia <nkadel at gmail.com> wrote: >> >> It's default behavior for the Nomachine Windows client. When you close >> it, it asks if you want to "disconnect" or "terminate" the session. >> Whether it works well is heavily dependent on the server, whether >> Neatx, FreeNX, or the NoMachine server. > > Please extend your remarks about which server you think is best and why. > > thanks/ldvLarry, please check the archives. I already covered that.