On Fri, Jun 21, 2013 at 8:10 PM, dv1...@wayne.edu wrote:
On Fri, Jun 21, 2013 at 04:02:59PM +0200, björn wrote:
On Fri, Jun 21, 2013 at 7:46 AM, dv1...@wayne.edu wrote:
Could it be because MacVim has TWO 'configure' files of substance, while
BramVim only has one?
In MacVim repo:
On Fri, Jun 21, 2013 at 8:52 PM, Blake Sweeney wrote:
On Tue, Jun 18, 2013 at 09:33:28PM +0200, björn wrote:
It sounds a bit like it could be a bug in MacVim's implementation of
the signs feature, but I don't ever use this myself so haven't noticed
any problems.
Can you create a minimal set
On Friday, June 21, 2013 6:57:51 AM UTC-7, björn wrote:
Thanks for the report. I've pushed a fix.
On Tue, Jun 18, 2013 at 6:41 PM, Bee fo...@calcentral.com wrote:
getfontname() seems broken is all versions of MacVim
I compiled MacVim version 7.3.1233 from
On Friday, June 21, 2013 6:57:51 AM UTC-7, björn wrote:
Thanks for the report. I've pushed a fix.
On Tue, Jun 18, 2013 at 6:41 PM, Bee wrote:
getfontname() seems broken is all versions of MacVim
I compiled MacVim version 7.3.1233 from
https://github.com/b4winckler/macvim/
and
On Jun 23, 2013, at 1:56 PM, gmn dv1...@wayne.edu wrote:
I would certainly have done so, but not being a programmer, I didn't
know that that is in fact the correct solution. For all I knew, there
may have been a very good reason for there to be two different, meaty
configure scripts.
On Sun, Jun 23, 2013 at 04:13:44PM +0200, björn wrote:
OK, I've restored the src/configure script from upstream now.
Tested and works.
Thanks again.
-gmn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
