Dave Feustel wrote:
Have you tried pasting into vim running in an xterm session? (Past the text by going into insert and then pressing shift+insert).
Yes - running vim outside screen (xterm, gnome-terminal etc.) works fine. Running it in screen, in either an xterm or a gnome-terminal gives the problematic behaviour. Xorg CPU usage is noticably higher with gnome-terminal and the delay (several minutes for gnome-terminal) between pasting and some text appearing in the editor feels slightly less, but the same basic problem persists.
There is no problem when pasting into vim running in a plain xterm (no screen).
Regards, Bryn.
Bryn M. Reeves wrote:
Dave Feustel wrote:
Have you tried pasting into vim running in an xterm session? (Past the text by going into insert and then pressing shift+insert).
Yes - running vim outside screen (xterm, gnome-terminal etc.) works fine. Running it in screen, in either an xterm or a gnome-terminal gives the problematic behaviour. Xorg CPU usage is noticably higher with gnome-terminal and the delay (several minutes for gnome-terminal) between pasting and some text appearing in the editor feels slightly less, but the same basic problem persists.
There is no problem when pasting into vim running in a plain xterm (no screen).
This may not solve your problem, but just in general I find it much nicer to use freenx and the NX client from www.nomachine.com for the things I might otherwise have done with screen. That is, leave a desktop running under freenx on a stable, well connected machine with an assortment of terminal windows, perhaps ssh'd to other systems. You can disconnect the NX client with everything running and reconnect later even from other locations just like screen except with a full GUI desktop and very good remote performance after the initial screen draw. If you haven't tried it, it is much more responsive on remote connections than other remote X approaches and cross platform clients are easy to install.
Les Mikesell wrote:
This may not solve your problem, but just in general I find it much nicer to use freenx and the NX client from www.nomachine.com for the
Thanks for the suggestion but that's not really an option here - many of the systems I'm logging into don't have the requisite bits available to use freenx and are not under my direct control. Using one host as a "gateway" where all the terminal windows live would also be a bit restrictive for the way that I work.
I'm guess I'm pretty settled in my ways with screen etc. and it fits nicely into the way I like to organise my work. Screen did not have this behavior back in FC6, so it appears that something changed in the meantime.
If you haven't tried it, it is much more responsive on remote connections than other remote X approaches and cross platform clients are easy to install.
I've tried FreeNX and for what it does, it's definitely a big step up from vnc etc., but I'd still like screen to work the way it used to - it's a bit of a "from my cold dead hands" issue I guess :-)
Regards, Bryn.
-
Bryn M. Reeves -
Les Mikesell