On 15 August 2010 06:43, James Cox wrote:
Here's the line that caused it, in ~/.vimrc
autocmd VimEnter * set background=dark notitle noicon
i don't recall that i wrote that-- does macvim drop a .vimrc when one
doesn't exist?
No. MacVim never touches any of your config files. I'm afraid
Björn Winckler wrote:
This does not look good (in os_macosx.m):
#if defined(FEAT_CLIPBOARD) !defined(FEAT_GUI)
It means the clipboard code will not get included when I compile
MacVim (since it defines FEAT_GUI). I think you meant FEAT_GUI_MAC,
right?
Hmm, I suppose it's
On 15 August 2010 21:32, Nikola Knezevic wrote:
On Aug 15, 8:54 pm, björn wrote:
I took a look at the code. I can't figure out why the problem occurs,
but I solved it by using double-fork(). This way, I ensure that MacVim
process becomes a child of init. Double fork()-ing is often used when
Hi MacVim users,
I have uploaded a build of MacVim 7.3 to:
http://github.com/b4winckler/macvim/downloads
(If you are running a 7.3 BETA build you can update via the MacVim -
Check for updates... menu.)
This is a stable build which at the moment it only supports Mac OS X
10.6+. The changes
Dennis Preiser wrote:
Bram Moolenaar b...@moolenaar.net wrote:
I encountered a drawing issue with:
| hi CursorLine gui=underline guisp=gray
set. This should underline the current line with a gray line from the
left edge to the right edge. When displaying help files sometimes the
Björn Winckler wrote:
Hi MacVim users,
I have uploaded a build of MacVim 7.3 to:
http://github.com/b4winckler/macvim/downloads
(If you are running a 7.3 BETA build you can update via the MacVim -
Check for updates... menu.)
This is a stable build which at the moment it only
