I'm using GVim on a Surface Pro 3 that has a touch screen. I've gotten so used to scrolling windows (like the browser) using the touch screen, so I thought it would be nice to be able to do the same in GVim. However, when I drag my finger it selects text rather than scrolling. Is there a way to change that?
Whohooo, my first tumbleweed badge. :-) Anyway, this actually works out of-the-box with the Vim build from https://bitbucket.org/Haroogan/vim-for-windows
Related
i'm a new vim user since 2 weeks and i've currently have my biggest trouble for the moment on vim.
i always have a x and y scrollbar on my vim and the x one is very anoying because it cover my commands.
here is a screenshot of the scrollbars that appears when i use terminal inside of vim using `:term` / `:!dir` or even when i save my vimrc or source it (`:so ~/.vimrc`)
if there is any solutions to it i will be really grateful, thanks for reading
This is an issue with your layout settings in Powershell and Ubuntu. Right click on the top bar of either program, go to Properties and then go to the Layout tab. You can check the Wrap text output on resize box and that should get rid of your horizontal scrollbar, thereby allowing you to use Vim as normal. Alternatively, in the same menu, you can decrease the width of the screen buffer size so that it is smaller than the width of the window size.
I love the mod4 + mouse-drag combo for moving/resizing windows in Awesome WM, it's very intuitive with regular mouse. Now that I'm using Awesome WM on my laptop, however, I find this combo more annoying when using the touchpad vs regular mouse.
The problem stems from the fact that I now need 3 fingers to perform a gesture that I could do with 2 before (1 to move on the touchpad, 1 to keep on the left-click at all times, and one on mod4). Alternatively, I can apply more force to the touchpad and have it pressed as I drag my finger, which is not any better since it puts a lot of stress on the finger doing the dragging).
What I would like to do instead is have awesome treat left-mouse button as pressed if both of the following conditions are met:
mod4 is pressed
movement event is coming from touchpad and not regular mouse
To do so, however, I need to be able to detect that the movement is coming from the touchpad. Is there a way to do so in Awesome WM/Linux? I've looked through the keysyms (http://wiki.linuxquestions.org/wiki/List_of_keysyms) but don't see anything for the mouse. I've also looked at the mouse.lua file in Awesome WM but it doesn't seem to have anything to differentiate between the two either (https://github.com/awesomeWM/awesome/blob/master/lib/awful/mouse/init.lua). If there is a way to tell that the last coordinate change came from a touchpad on Linux that would resolve the issue as I could simply create a lua file to run such check whenever Mod4 is pressed.
To do so, however, I need to be able to detect that the movement is coming from the touchpad. Is there a way to do so in Awesome WM/Linux?
Nope, there is no such way in AwesomeWM. Sorry.
In X11, this is possible via the input extension. However, awesome does not use that extension.
I've just recently begun experimenting with urxvt as a terminal emulator rather than xterm. I'm a heavy tmux user, so having both work seamlessly together is a must.
I've noticed that when running tmux inside urxvt, there is some odd behavior when selecting text. I hold shift, use the mouse to select text, and the text is highlighted in yellow (as if tmux is still handling it) but then blinks and flashes to a black background -- almost as if urxvt and tmux are competing for control of the selection. Does that make sense?
I've test this with zero (except enabling the mouse in tmux) personal configuration options in both tmux and urxvt.
In xterm, when I would hold shift and select text I would notice that it would highlight in reverse colors (as opposed to tmux's yellow background). In urxvt, the selected text still seems to be controlled by tmux.
Any ideas on how to fix this weird behavior?
I'd even be interested in some tips or keywords on how to uncover the problem here. Any developers familiar with the codebase that understand why mouse-selection works fine in xterm, but not with urxvt term?
Thanks to nicm from this issue in the tmux's github repository, the problem you described was solved for me (for tmux 2.1 and urxvt 9.21):
You can disable tmux entering copy mode when dragging by unbinding the
MouseDrag1Pane key binding.
In .tmux.conf, add:
unbind -n MouseDrag1Pane
I recently started using Lisp and Limp is the only available plugin for VIM. But, once I set it up and hit F12, the terminal like window that appears has a very small font size. I have a screen resolution of 1920x1080 and it's impractical to read such small fonts. I went through the man page of 'screen', but couldn't find any useful information on changing the font or font size. Is there a way to do this?
And how about using something like 'xterm' rather than 'screen'? I looked through the code of bridge.vim. I don't think it is too much of a task. Any ideas on this?
By screen, do you mean GNU screen?
GNU screen is a terminal emulator that runs in another terminal or emulator. It has no direct control over font sizes; it's purely text based. The window you're seeing must be some GUI terminal emulator; you haven't told us enough to guess which one (could be xterm, could be Gnome terminal, etc.).
For xterm, control-right-click should bring up the "VT Fonts" menu, which will let you select a different font. If none of the available fonts are to your liking, you can use X resources to reconfigure the options, including the choice for the default font.
xterm also supports a control sequence that sets the current font. You have to know the name of the font you want. xlsfonts will show you a very long list of font names (it just showed me 5594 of them). For example, if you run this from a shell running in xterm:
printf '\e]50;-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1\a'
it should give you the font I usually use. But screen generally intercepts escape sequences like that, so it probably won't work from screen under xterm.
Other terminal emulators should have similar mechanisms.
I've been trying to get colourschemes to work properly in VIM when using it over ssh with PuTTy as a client but unfortunately I haven't had much success. I can only get 8bit colours working with PuTTY even though I've enabled 256 colors in putty and set t_Co=256 in VIM. They don't turn out as they should. I've been trying to replicate this setup http://www.interworksinc.com/blogs/ckaukis/2009/06/03/vim-color-schemes-putty but as I say it's been in vain so far.
Has anyone here had success with colourschemes working with VIM in PuTTy? I'd appreciate any advice
Thanks,
Patrick
[EDIT] Turns out I've found the source of the problem. I was using vim in a screen which was breaking the colours. Updated question I guess is, is it possible to have working colors in a screen session? [/EDIT]
As well as compiled support, it may be necessary to add some config to screenrc (I needed to).
http://www.frexx.de/xterm-256-notes/ has a good guide. The relevant part to screen:
By default, screen is not aware that it is running in a 256 color capable xterm. To make programs in screen recognize this feature, you need to set three things in your ~/.screenrc:
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
# erase background with current bg color
defbce "on"
Yes, you can do 256 colours with screen, however, this option usually isn't compiled in. Simply compile screen yourself with:
--enable-colors256
Alternatively, you could get a tabbed PuTTy. It has the advantage of ctrl-a going to the beginning of the line, and saves you from many termcap headaches. However, if you like to reconnect to your screen sessions from multiple terminals, there really isn't anything better than screen for the job.
NB. This question probably belongs on Superuser.
I had same problem on Mac Os, tried some solutions but all tests show that 256 colors not displayed. After that I'm installed screen from brew and all works great. Maybe it's because Mac Os default screen from /usr/bin/ compiled without --enable-colors256 flag.
Solution for mac os: brew install screen
I had trouble with black background in Putty: blue characters on a black background with default colours are hard to read:
My solution for a better contrast was to enable "system colors" checkbox unter
"Settings / Window / Colours / Use system colors"
This displays the Putty screen with black characters on a white background. Not hip but readable :-)