Skip to main content

Vim: Transparency in MacVim


Wahoo! MacVim now supports transparency. Finally, I can have a nice, transparent Vim window to match my transparent terminal, and I don't have to give up all the modern conveniences. If you use the "Homebrew" profile for your Terminal.app, try putting the following in your .gvimrc:
colorscheme torte
set transparency=15

Comments

Unknown said…
thank you, since changing from Ubuntu to Mac at work, I have been using vim (interminal) because I could not have a transparent background in MacVim (or so I thought!)
You have mad my life just a little easier.
Daniel said…
Tried in both .vimrc & .gvimrc

All it does is fades the background color (making it more opaque to white)
jjinux said…
Are you using MacVim?
Anonymous said…
Yeah I can't get the background to be transparent either (and yes, using MacVim (on Lion))
jjinux said…
I'm sorry to hear that. Unfortunately, I don't currently have a Mac, so I can't help debug this. It might be worth a bit of googling.
Alex Blackie said…
I'm also on Lion, and didn't notice any transparency, but I think I've found the problem. The window itself isn't transparent, but the buffers are...

Observe: http://cl.ly/9rXo

You can see the other buffer in the background. So I guess, in Lion, transparency doesn't work properly...
Unknown said…
It will work if you turn on the experimental renderer (MacVim preferences -> Advanced tab). Via: http://code.google.com/p/macvim/issues/detail?id=278
Anonymous said…
Don Smith, thank you so much. Almost went back to terminal vim because of no transparency.
omaryahir said…
Thanks for this, first not work, but after make the two files in ~/.vimrc and ~/.gvimrc the two files with the same content, now, works very well, thanks a lot !!!

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p