I think there's a bug in MacVim that manifests when using its GUI form
but not when one calls it in the console. This bug doesn't affect
BramVim either. I have never seen this until Mavericks.
There is more than one way to reproduce it. I'm going to include at
least two such ways because it
On Wed, Oct 23, 2013 at 08:49:03AM -0700, Penn Su wrote:
In Mac since Lion I believe, they introduced the resume feature that would
let apps to resume the windows, and the unsaved documents state before
quitting. I wish macvim could also implement this feature so that whatever
windows or
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
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:
On Tue, Jun 18, 2013 at 09:27:17PM +0200, björn wrote:
On Thu, Jun 13, 2013 at 9:55 PM, wrote:
On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
On 05/27/13 at 10:46:11 -0400
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:
'configure' is just a tiny wrapper.
'src/configure' is meaty.
On Tue, Jun 18, 2013 at 09:27:17PM +0200, björn wrote:
I think it would be better to figure out why there is a difference
instead of blindly patching. I don't know what causes it though, so I
can't help.
Very well then :)
To all: don't use the '-C' flag with './configure', or else you will
Here on Tiger PPC I updated to 7.3.1148.
Here is a new compiler warning I haven't seen yet; it occurred during
the plain Vim portion of building MacVim.
In file included from regexp.c:7891:
regexp_nfa.c: In function ‘post2nfa’:
regexp_nfa.c:2754: warning: ‘end_state’ may be used
Here on Tiger PPC I updated to 7.3.1148.
Here is a new compiler warning I haven't seen yet; it occurred during
the plain Vim portion of building MacVim.
In file included from regexp.c:7891:
regexp_nfa.c: In function ‘post2nfa’:
regexp_nfa.c:2754: warning: ‘end_state’ may be used uninitialized in
On 05/27/13 at 10:46:11 -0400 gmn wrote:
In my opinion, whatever scripts in MacVim that control this ought to be
changed so that the result matches BramVim, and config.cache files will
go in src/auto rather than just src. That way, make distclean in a
MacVim repo will in fact clean them.
Two things, for the record,
1. To prevent any confusion with my other ongoing thread re Tiger PPC, I note
that this business about config.cache happens on all archs. I see it on Tiger
PPC, Leopard PPC, Lion and Mountain Lion.
2. Also, besides config.cache, the following files are put into
björn, on 05/27/13 at 08:22:23 +0200, wrote:
On Mon, May 27, 2013 at 2:02 AM, dv1...@wayne.edu wrote:
björn, on 05/24/13 at 15:35:52 +0200, wrote:
I had a look and there are two issues:
1. Py_VISIT was introduced in Python v2.4, perhaps Mac OS X Tiger is
including an older Python
Sorry for the delay; been out of town a few days with no computer.
björn, on 05/24/13 at 15:35:52 +0200, wrote:
I had a look and there are two issues:
1. Py_VISIT was introduced in Python v2.4, perhaps Mac OS X Tiger is
including an older Python version (otherwise I don't know why the linker
dv1...@wayne.edu, on 05/19/13 at 01:11:47 -0400, wrote:
Scrolling up through the terminal output reveals some warnings
that are potentially useful:
-pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1
Phil Dobbin, on 05/23/13 at 01:50:52 +0100, wrote:
On 19/05/2013 06:52, dv1...@wayne.edu wrote:
dv1...@wayne.edu, on 05/19/13 at 01:11:47 -0400, wrote:
MacVim failed to build on OS X 10.4.11 (PPC) after pulling to 7.3.967.
Everything as of the 7.3.806 pull from February was just fine.
Bram Moolenaar wrote:
Doing 'make distclean' doesn't remove src/config.cache. Shouldn't it?
I went to compare this to the BramVim repo, but found that the BramVim
repo's ./configure script never even creates src/config.cache in the
first place.
If I forget to do the export
Hi Björn,
MacVim failed to build on OS X 10.4.11 (PPC) after pulling to 7.3.967.
Everything as of the 7.3.806 pull from February was just fine. Seems
the recent fiddling with Python in BramLand has messed things up for
poor Tiger.
My ./configure flags are:
--with-features=big
Hi Björn,
Doing 'make distclean' doesn't remove src/config.cache. Shouldn't it?
I went to compare this to the BramVim repo, but found that the BramVim
repo's ./configure script never even creates src/config.cache in the
first place.
If I forget to do the export CC=clang bit before
dv1...@wayne.edu, on 05/19/13 at 01:11:47 -0400, wrote:
MacVim failed to build on OS X 10.4.11 (PPC) after pulling to 7.3.967.
Everything as of the 7.3.806 pull from February was just fine. Seems
the recent fiddling with Python in BramLand has messed things up for
poor Tiger.
I forgot to
björn wrote on 07/10/12 at 23:18:38 +0200:
On Sat, Jul 7, 2012 at 6:55 PM, dv1...@wayne.edu wrote:
I thought that (1) the outputs of both :r !ls and glob() should be
indentical, and also that (2) they should both do it the way that
!ls does it. The reason I think this is because that's
On 03/24/12 at 13:07 +0100, björn wrote:
On Tue, Mar 20, 2012 at 11:30 PM, wrote:
I think There is a bug in MacVim regarding multibyte characters. It
only happens when the Experimental Renderer is turned ON.
To reproduce:
1. make a new folder bar.
2. In bar, do touch föo, where
I think There is a bug in MacVim regarding multibyte characters. It
only happens when the Experimental Renderer is turned ON.
To reproduce:
1. make a new folder bar.
2. In bar, do touch föo, where there is an umlaut over the first 'o'.
3. Start MacVim with mvim -u NONE -U NONE.
4. In MacVim,
In the last couple of days I've seen false information about the purpose of
this list floating around, particularly the claim that questions not about
MacVim don't belong here.
This is not just a list for MacVim. This is a list for using vim on a Mac,
that is, for questions about vim having
Wrote Björn Winckler [07/27/11 @20:27:39 +0200]:
For those of you who are not charmed by Lion's full-screen, this one is for
you:
defaults write org.vim.MacVim MMNativeFullScreen 0
Thank you, thank you, thank you, thank you, thank you...
For those of you who, like me, like old fullscreen
It's wonderful that MacVim works with Lion already. I've built from the
lion branch, and noticed a few bugs or less-than-fully-desirable aspects
of Lion's native fullscreen wrt MacVim.
All of the following results even after doing mvim -u NONE -U NONE and
having no ~/.vim folder, except where
Let me add number 5 to the list:
5. Fire up MacVim and enter fullscreen. Then do :w. See the MacVim window
disappear. See the plain gray background remain; MacVim is not releasing the
Space it claimed while in fullscreen mode. I can find no way to get rid of
this extra, gray Space besides
25 matches
Mail list logo
