Dennis Preiser wrote:
> Bram Moolenaar 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
On Sun, Aug 15, 2010 at 4:43 PM, björn wrote:
> Hi MacVim users,
>
> I have uploaded a build of MacVim 7.3 to:
>
> http://github.com/b4winckler/macvim/downloads
Excellent.
Congrats, and thank you!
--
Ed Marczak
e: marc...@radiotope.com
w: http://www.radiotope.com/writing
MacTech Conference: htt
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 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
Hello Vim users,
Announcing: Vim (Vi IMproved) version 7.3
This is a minor release of Vim. It consists of Vim 7.2 plus all
patches, updated runtime files and some more, see below. It has been
two years since the 7.2 release, thus it's not that "minor". But not
"major" either. Something in
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
> > you want to make sure that the child d
On 15 August 2010 19:58, Nikola Knezevic wrote:
>> > I debugged the problem and found that it is caused by calling setsid()
>> > when forking but have no idea why this is [2]. It is called from
>> > macos_fork() inside src/os_macosx.m in case you feel like debugging
>> > the issue. I'd appreciate
On Aug 12, 3:51 pm, Nikola Knezevic wrote:
> > I debugged the problem and found that it is caused by calling setsid()
> > when forking but have no idea why this is [2]. It is called from
> > macos_fork() inside src/os_macosx.m in case you feel like debugging
> > the issue. I'd appreciate the hel
On Sun, Aug 15, 2010 at 6:18 AM, björn wrote:
> 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?
>
>
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?
> >
> >
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 a
12 matches
Mail list logo
