When a file is opened within iTerm using vim, light white shadow overlays the entire screen making the text unreadable.
How can I get this fixed?
Open within iTerm:
Open in vim app:
It's related to the theme that you chose in iTerm2.
As alex said, feel free to play around with the iTerm2' color settings.
Related
Just to clarify, I'm not talking about making the background of the editing frame or window dark via:
local G = ...
styles = G.loadfile('cfg/tomorrow.lua')('Zenburn') -- theme
I'm talking about making the background of the Project frame/window, Output window, the menu bar, etc., all dark too.
Is this possible to do without using Windows's high-contrast theme for everything?
Thank you.
I don't think this is possible, as it relies on wxwidgets to draw those windows and wxwidgets uses system-provided colors to draw them (without much if any user control).
I opened a wxwidgets ticket that would implement re-configuring system colors, but there hasn't been much movement on it.
I have the solarized theme working in a terminal vim session. It looks great at first until you move off page and black space appears. If you then scroll back up the black space is also in the originally colored areas... The colors do not change if you use page up page down, only j,k
What the error looks like:
You do not have the the solarized dark theme working in your terminal Vim session. I can tell because your background is black/dark gray. The solarized dark background is dark blueish.
To get the solarized colorscheme to work properly within your terminal emulator you have to change the color settings of your terminal emulator to solarized.
How to do so depends on which kind of terminal emulator you use. With gnome-terminal, you can set the colors to solarized this way: Edit - Profile Preferences - Colors - Palette - Builtin schemes: solarized. For other terminal emulator use Google to figure out how to change the terminal emulator color.
Note that this of course also changes the colors displayed in your normal shell - but this is necessary and advised.
The problem was caused by the Background Color Erase of the terminal
fixed by adding the line
set t_ut=
see for further details
further details
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
I'm using TextEdit to transcribe sections of 26 moleskine notebooks that I've filled up over the past 7 years. I changed the background to black and the text color to gray, which is great for the eyes except I cannot see the cursor. This makes it hard to edit, as you can imagine. When I use textwrangler or sublime the cursor blinks white..how do I extend these settings to textedit?
Thank you - first ever stackoverflow question :)
Unfortunately it looks like TextEdit does not allow configuring the color of the cursor.
Is there a way to change the cursor color in TextEdit?
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 :-)