Re: [screen-devel] screen + tcsh
Sure, I have already asked about this (here, in -users mail list or in bug report on gnu.org, just can't remember where) There is text of bug report with removing lines issue: -- When running vim inside screen pressing ctrl+arrow_left or ctrl+arrow_right simultaneously deletes several lines of text. This does not happen when running vim directly in xterm for example. A workaround seems to be to add "set term=xterm" in .vimrc, but that may have various side effects. Steps to Reproduce: 1. # screen 2. # vim /etc/resolv.conf 3. hit ctrl + arrow_right Actual results: multiple lines of text get deleted Expected results: nothing happens -- I am not sure, if this issue was even correctly reported to screen, or if it is problem of vim or anything else. Josef - Original Message - | From: "Amadeusz Sławiński" <am...@asmblr.net> | To: screen-devel@gnu.org | Sent: Wednesday, October 19, 2016 5:23:54 PM | Subject: Re: [screen-devel] screen + tcsh | | On Wed, 19 Oct 2016 10:47:12 -0400 (EDT) | Josef Ridky <jri...@redhat.com> wrote: | | > term=xterm is used for avoiding to remove lines in vim when is | > pressed some specific key combination. | > | | Do you have any example of such combination? | | | Amadeusz | |
Re: [screen-devel] screen + tcsh
On Wed, 19 Oct 2016 10:47:12 -0400 (EDT) Josef Ridkywrote: > term=xterm is used for avoiding to remove lines in vim when is > pressed some specific key combination. > Do you have any example of such combination? Amadeusz
[screen-devel] screen + tcsh
Hi, I would like to ask for one thing about keybinding in screen. Following problem is the reason, why am I asking: --- Description of problem: The home and end keys no longer work in screen when using tcsh as shell. Steps to Reproduce: 1. start screen: $ screen 2. start tcsh $ tcsh 3. make sure home and end are bound: $ bindkey | egrep '^(home|end)' home -> beginning-of-line end-> end-of-line 4. press home or end Actual results: pressing "home" and "end" prints a "~". Expected results: cursor jumps to the beginning or end of the line. --- I think, that this behavior is caused by using 'term=xterm' in config file. Problem is, that this line has to be in the config file, because it solves other, much worse problem. Does anyone know, how to solve this without removing term=xterm? Thanks for your ideas. Regards Josef Ridky Associate Software Engineer Core Services Team Red Hat Czech, s.r.o.