[opensuse] unusable konsole for starting vim
i recently upgraded to leap 15.2 and now konsole has become horrible -- every instance of vim i start from konsole, whether gui or terminal, has almost all of its F-keys horribly and inexplicably redefined can anyone tell me how to make konsole usable again? tp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2020 05:27, tooth pik wrote:
i recently upgraded to leap 15.2 and now konsole has become horrible -- every instance of vim i start from konsole, whether gui or terminal, has almost all of its F-keys horribly and inexplicably redefined
can anyone tell me how to make konsole usable again?
tp
Before I'd add that to my 'yet another reason not to upgrade to Leapt 15.2" ongoing 9or it it on-growing) list, I'd try to determine if this is is a Konsole issue or a VIM issue. Behind the scenes, VIM starts by loading /usr/share/vim/vimrc (or in graphics mode as gvim, it loads /usr/share/vim/gvimrc) (and then there's the local versions, ~/.vimrc and ~/.gvimrc) and then there are the 'language' files ... Any of those might be changed and result in a change the way {g}vim works. Now I have an array of Konsole tabs. I start VIM in the leftmost and then key "shift+right-arrow". The context moves to the Konsole tab to the right. This is what I expect. It is Konsole behave. I'm running under KDE so that later intercepts and dispatches keys first. RTFM. Are you sure that is not your problem? SO, please give details, What do you expect the F-keys to do and what do they end up doing? Tell us that and we can start to think abut whether this is a KDE level, Konsole level or VIM level interpretation of the key. I ask this because you are saying "its not doing what I want/expect" but you aren't telling up either what it IS doing nor what you EXPECT. -- Context is Everything -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
a prime example is S-F3, which in my ~/.vimrc is mapped to :quall
what i expect to happen when i hit S-F3 is that vim exits all buffers
-- what actually happens
is focus is moved to the first line of the current buffer, the line is
erased, and i am left in
insert mode
i've started using xterm which isn't as pretty but the instances of
vim i start from it have their
expected mappings
and now, having started konsole and started gvim i see all my mappings
intact -- apparently
something got fixed with the 'zypper up' i did yesterday -- also i
stopped getting those annoying
'no protocol provided' messages whenever i start something
so -- sorry for the noise -- never mind!
On Fri, Sep 11, 2020 at 6:55 AM Anton Aylward
On 11/09/2020 05:27, tooth pik wrote:
i recently upgraded to leap 15.2 and now konsole has become horrible -- every instance of vim i start from konsole, whether gui or terminal, has almost all of its F-keys horribly and inexplicably redefined
can anyone tell me how to make konsole usable again?
tp
Before I'd add that to my 'yet another reason not to upgrade to Leapt 15.2" ongoing 9or it it on-growing) list, I'd try to determine if this is is a Konsole issue or a VIM issue.
Behind the scenes, VIM starts by loading /usr/share/vim/vimrc (or in graphics mode as gvim, it loads /usr/share/vim/gvimrc) (and then there's the local versions, ~/.vimrc and ~/.gvimrc) and then there are the 'language' files ...
Any of those might be changed and result in a change the way {g}vim works.
Now I have an array of Konsole tabs. I start VIM in the leftmost and then key "shift+right-arrow". The context moves to the Konsole tab to the right. This is what I expect. It is Konsole behave. I'm running under KDE so that later intercepts and dispatches keys first. RTFM. Are you sure that is not your problem?
SO, please give details, What do you expect the F-keys to do and what do they end up doing?
Tell us that and we can start to think abut whether this is a KDE level, Konsole level or VIM level interpretation of the key.
I ask this because you are saying "its not doing what I want/expect" but you aren't telling up either what it IS doing nor what you EXPECT.
-- Context is Everything
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/11/20 12:35 PM, tooth pik wrote:
i've started using xterm which isn't as pretty but the instances of vim i start from it have their expected mappings
Side note: You can "Prettify" xterm by creating a ~/.Xresources file, e.g. xterm*termName: xterm-256color Xterm*saveLines: 8192 XTerm*metaSendsEscape: true xterm*VT100.geometry: 120x58 xterm*faceName: DejaVu Mono:size=9:style=book:antialias=false xterm*font: 7x13 XTerm*colorBDMode: true XTerm*scaleHeight: 1.01 xterm*background: #000000 xterm*foreground: #c8c8c8 XTerm*scrollBar: true XTerm*rightScrollBar: true (https://wiki.archlinux.org/index.php/Xterm -- adjust to taste) And you can get rid of the annoying bell and set the typematic rate in ~/.xprofile xset -b xset r rate 276 50 see: man xset Hope that helps with xterm. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 11 Sep 2020 12:35:30 -0500
tooth pik
i've started using xterm which isn't as pretty but the instances of vim i start from it have their expected mappings
FWIW, in addition to David's suggestions to customize xterm, you could also just use lxterminal instead or even gnome-terminal (though I haven't used the latter in a while and it may have bitrotted). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
Dave Howorth -
David C. Rankin -
tooth pik