Hi,
Great response. Thanks guys.
I forgot to say that Douglas is taking over maintenance (thanks to
amadeusdemarzi who also offered to help). Douglas has been releasing
snapshots for older versions of OS X for a while now so it is great
that he'll take over.
Best wishes,
Björn
P.S. Douglas, I
be able to find enough time to keep up.
If anybody is interested in taking over as maintainer, please let me
know and I'll fill you in on the workflow I've used to update Vim
patches and release snapshots etc.
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type
occur
Running MacVim snapshot 73 (Vim 7.4.258) on OS X 10.9.2
Have you by any chance got two (or more) MacVim.app on your hard
drive? Search in Spotlight for MacVim.app and delete all but one
(and make sure it is in /Applications).
Björn
--
--
You received this message from the vim_mac
borked.
Thanks for all the good work!
-Ian
I tried it out as well and ran into the same problem. For the moment
you'll have to resort to using the conceal feature instead.
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_mac group
Hi,
I've built a new snapshot of MacVim to update to the latest Vim patch level:
https://github.com/b4winckler/macvim/releases
Björn
--
--
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 information, visit
through
https://github.com/b4winckler/macvim/wiki/Troubleshooting
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message
, but it
doesn't seem like it should be impossible to implement.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because
'unnamedplus' is
seemingly not a feature, so it returns 0 for me.
These are X11-specific features which is probably why its not working
they way you expect and why has('unnamedplus') returns 0. You may
be able to compile vim with the gtk gui to use them on OS X.
Björn
--
--
You received
Metadata.framework [Error]: void
_MDItemMarkAsUsedForPath(CFStringRef): was called with a NULL path
It's a private API related to file metadata, but I don't know what it means.
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you
/releases and see if that works.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google
On Mon, Oct 21, 2013 at 12:14 AM, Felix Buenemann wrote:
Am 19.10.2013 um 18:54 schrieb björn:
On Sun, Oct 13, 2013 at 11:16 PM, Felix Bünemann wrote:
Am Mittwoch, 9. Oktober 2013 20:25:49 UTC+2 schrieb björn:
On Wed, Oct 9, 2013 at 12:18 AM, Felix Bünemann wrote:
I'm pretty sure
On Fri, Oct 25, 2013 at 11:23 PM, Bee wrote:
On Friday, October 25, 2013 11:23:02 AM UTC-7, björn wrote:
...
Since I've upgraded my Mac to OS X 10.9 I will from now only be
maintaining binaries for this version of OS X. If anybody wants
to provide binaries for OS X 10.6 (which I used to build
On Fri, Oct 25, 2013 at 8:34 PM, björn wrote:
On Fri, Oct 25, 2013 at 8:26 PM, Michael Grubb wrote:
Yes there are run-time warnings:
Oct 25 13:25:53 macbook MacVim[15393] Error: The function `CGContextErase'
is obsolete and will be removed in an upcoming update. Unfortunately
glyphs. This was one of the big reasons why I switched to make the
Core Text renderer the default.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
from those APIs in the future.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed
to be the case).
Björn
P.S. A reminder to everybody on this list to please refrain from top
posting. That is, type your reply below the text you are replying to
and remove irrelevant text from the original. Thanks!
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your
update to snapshot 72 that was just released and let us know if
the problems persist.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received
test builds seem to work fine -- I've not encountered any problems
with Ruby with the little testing I've done so far.
Björn
--
--
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 information, visit http
On Sun, Oct 13, 2013 at 11:16 PM, Felix Bünemann wrote:
Am Mittwoch, 9. Oktober 2013 20:25:49 UTC+2 schrieb björn:
On Wed, Oct 9, 2013 at 12:18 AM, Felix Bünemann wrote:
I'm pretty sure that AvailabilityMacros.h is available on all versions of
OS
X, because it's copyright header states
. This is due to the fact that drawing commands have to cross a
process boundary.
I will take a look when I get the time, but it will be a while. Feel
free to open an issue on the Google code page as well to reduce the
risk that I forget about this, but that is up to you.
Thanks,
Björn
--
--
You
--startuptime start.txt). To me that is more than fast
enough...
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message
it.
My sincere apologies for disrupting your workflow, I'll make sure this never
happens again.
Thanks Douglas!
I've been bitten by something similar in the past when I was running
MacPorts so I know how easily these things can happen...
Björn
--
--
You received this message from the vim_mac
installed, but thanks Kai for investigating and pointing this
out!
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message
other key though (Cmd+Shift+Q? Ctrl+Q?).
Other than that you'd have to edit the source code, but getting the
number of open splits from Vim inside the MacVim process is probably
going to be a bit tricky.
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your
version 7.4
- I have removed all of my configuration files and plugins (.vimrc, .gvimrc,
.vim) and still have the issue
Have you tried deleting ~/.viminfo? (Make sure Vim is not open before
doing so.)
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your
be supported. If there is a suitable #ifdef
check for that, then it should be possible to submit as a patch to
mainline Vim.
Björn
--
--
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 information, visit http
AvailabilityMacros.h ... uh, unless Apple forces the use of
Availability.h in the future ... I guess we'll have to deal with it
then). This way everybody on OS X 10.9 can at least pull from the
MacVim repo and build Vim / MacVim from there.
Thanks for the patch,
Björn
--
--
You received this message from
and install MacVim.
Björn
[1] https://github.com/b4winckler/macvim/wiki/Building
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message
://github.com/b4winckler/macvim/releases
Currently, there is only a build targeted for OS X 10.6. OS X 10.7 and
10.8 builds will be added later.
Björn
--
--
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
to improve Vim!
Best wishes,
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google
On Wed, Aug 7, 2013 at 7:32 PM, Fuad Saud wrote:
Is there a way to use metal tabs on fullscreen?
Sure, search for setStyleNamed inside src/MacVim and change Unified
to Metal (there seem to be two of them), then recompile [1].
Björn
[1] https://github.com/b4winckler/macvim/wiki/Building
at the system level, try pressing
Ctrl+F7 to toggle/enable full Tab navigation.
That setting is also accessible in System Preferences-Keyboard-**
Keyboard Shortcuts, towards the bottom of the pane.
In addition to this, take a look at :h macvim-dialogs.
Björn
--
--
You received this message
splits, the command line, etc, so I'm not sure how
useful it is.
The source code (of which the MacVim part is Objective-C and core Vim is C)
is at https://github.com/b4winckler/macvim.
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text
On Thu, Jul 25, 2013 at 8:49 PM, Fuad Saud wrote:
Just curious. These fullscreen tabs are really out of fashion :\
Because it was decided that the metal tab style only looks good when
there is a window frame.
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post
-- are
you using the latest snapshot? If not, try updating. Also, go through the
Troubleshooting guide [1].
Björn
[1] https://github.com/b4winckler/macvim/wiki/Troubleshooting
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you are replying
sure that the problem is in MacVim, and not in vim itself.
I've attached a couple of representative logs. Björn, if you'd like
issues created for these, I'd be happy to do that; I just figured I'd ping
the list first in case you'd prefer to triage them e.g. one at a time, as a
group
is modified (it may e.g. cause scrollbars to hide/show).
So, it seems to be related to vertical splitting. Perhaps there is a
better way to solve the problem?
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you are replying
Code page when I get a chance.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google
On Mon, Jul 8, 2013 at 10:26 PM, Douglas Drumond
drumond.doug...@gmail.comwrote:
On Mon, Jul 8, 2013 at 4:42 PM, björn bjorn.winck...@gmail.com wrote:
My current advice is - anybody who can't live with it should disable the
Core Text renderer (but the speed of the default renderer may put
screenshot, although minor (parts of the window got blurry
during resizing, but got back to normal when resizing stopped). Disabling
core renderer in Preferences → Advanced and reopening the window made the
problem go away. I have no clue on how to solve it (Björn, can you give me
some pointers
On Sat, Jun 29, 2013 at 12:28 AM, Jimmy Zelinskie wrote:
On Friday, June 28, 2013 2:33:19 AM UTC-4, björn wrote:
On Thu, Jun 27, 2013 at 10:01 PM, Jimmy Zelinskie wrote:
As per the discussion at
https://github.com/mxcl/homebrew/pull/20831#discussion_r4917643
The required macro
kindly provided binaries of snapshot 67 for 10.7 and
10.8, which are now available at
https://code.google.com/p/macvim/downloads/list
Enjoy!
Björn
--
--
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 information
have uploaded a build of MacVim (snapshot 67) based on Vim 7.4a BETA:
https://code.google.com/p/macvim/downloads/list
This build is for SNOW LEOPARD (10.6) and later versions of OS X. (I will
build a version targeted specifically for 10.8 on Monday, most likely.)
Björn
--
--
You received
this patch address and is there perhaps a
better way to solve it?
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message
).
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_mac group
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
Thanks for the report. I've pushed a fix.
Björn
On Tue, Jun 18, 2013 at 6:41 PM, Bee fo...@calcentral.com wrote:
Björn
getfontname() seems broken is all versions of MacVim I have tried. It
returns nothing. This came up in a vim_use thread:
Macvim seems not to be reading my .vimrc
http
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 gmn wrote:
In my opinion, whatever scripts in MacVim
...).
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_mac group
)
If it isn't an easy thing, just forget it. I can deal with it.
Hi Björn,
Although I discovered how to trigger the issue, I don't know what causes
it. I don't know enough about makefiles or confiure scripts to wade
through the difference between those of MacVim and those of BramVim. So
I
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 of step-by-step instructions on how to
reproduce (preferably using only Syntastic and Vim)? Attach a file if
necessary.
Thanks,
Björn
--
--
You
- bibtex is working with MacVim
- \cite{ F9, works with MacVim, when thebibliography is in the tex file
x \cite{ F9 doesn't work with bibtex and MacVim
Do you have any ideas, how to fix this?
I think you have to ask the plugin authors for help trying to localize
the problem.
Björn
--
--
You
it works?
I think you should try posting this to the vim_use Google group. It
sounds like a general Vim problem and not specific to Vim on the Mac.
Björn
--
--
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
is super-slow on Mountain Lion whereas on
Snow Leopard it was fast. (That is also why I couldn't reproduce to
begin with.)
Björn
--
--
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 information, visit http
is the easy
part -- how to deal with the fact that Vim is an application and not
just a view will require more thought (I have no good solution, and
I've spent some time thinking on this).
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you
, then
you have a plugin or [g]vimrc setting that is interfering.
Other things I can think of is that you may be using a keyboard layout
that causes problems. If you're not using an English layout, try US
English and see if that works.
Björn
--
--
You received this message from the vim_mac maillist
I make a new snapshot. I don't intend
to add Lua support as this just complicates the build process, so you
should build your own version [1].
Björn
[1] https://github.com/b4winckler/macvim/wiki/Building
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your
On Sat, Jun 8, 2013 at 12:56 PM, Bram Moolenaar wrote:
Björn wrote:
On Thu, Jun 6, 2013 at 4:11 PM, Jakub Turski wrote:
Is there a chance to get a new snapshot of Macvim available for download?
Preferably with Lua support compiled in and patch level above 7.3.885 so
people can use
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 version (otherwise I don't know why the linker
. I'm not sure what the policy on being backwards
compatible with older Python versions is.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You
config.cache in src/. Not sure why you do but as far as I can
tell MacVim is not the cause of this. There should not be any reason why
it should create this file (at least I never patched the configure script
to do so).
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post
undertaking.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_mac group
, and related files out of the way?
- Have you tried moving .vim/.vimrc/.gvimrc out of the way and started
MacVim by clicking its icon in Finder (make sure you've quit MacVim
completely first)?
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below
folder, .vimrc/.gvimrc files) out of the way before trying
again.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message
Save that to a text file (e.g. beval.vim) and source it (:so
beval.vim) -- this should cause a balloon to pop up showing the word
under the cursor. It works as expected for me.
Björn
--
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you
. The AppleScript is only run if required - to keep things fast.
Initially that sounds sort of useful, but I'm guessing it adds to the
startup time a bit which is bad. In that respect, isn't it better to
just install MacVim to /Applications or just set VIM_APP_DIR if that
is not possible?
Björn
I can't reproduce with iTerm2 1.0.0.20130302 on OS X 10.6.8 with
MacVim snapshot 66. Is it perhaps related to a specific colorscheme?
Which one are you using? I'm using desert and started with
COLORFGBG=7;0 mvim
since that variable is unset by default on my computer.
Björn
On Thu, Mar 14
I tried creating a simple file with tabs in it but did not experience
the slowness you mention. Can you please send me a file where the
problem occurs for you so that I have something to test with?
Thanks,
Björn
On Wed, Mar 13, 2013 at 11:16 PM, Kevin Burke ke...@twilio.com wrote:
Hi,
I've
.
Björn
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_mac group
I think I (capital I) is what you're looking for.
Björn
On Fri, Feb 22, 2013 at 10:31 AM, WenMin Tu shoeme...@gmail.com wrote:
using visual block mode to select few lines(I tried CTRL+v, v, V, CTRL+q),
and I tried to using i to insert some chars in front of every selected
line, but turns
try asking on vim_use as it
has more people reading (and helping) with these types of problems.
Good luck,
Björn
[1] https://github.com/b4winckler/macvim/wiki/Troubleshooting
On Mon, Feb 18, 2013 at 5:38 AM, David Gillooly
david.gillo...@gmail.com wrote:
Somehow I have gotten MacVim to capitalize
Very interesting to hear that you managed to work around this issue.
I've added your comment at
https://code.google.com/p/macvim/issues/detail?id=363
Björn
On Tue, Feb 12, 2013 at 8:51 PM, Niels Kobschätzki
ni...@kobschaetzki.net wrote:
On 11 Feb 2013, at 21:30, Niels Kobschätzki wrote:
Hi
There is a thread regarding this problem at [1]. Maybe you can help
out by generating a debug log as I asked in that thread.
Thanks,
Björn
[1] http://code.google.com/p/macvim/issues/detail?id=363
On Thu, Jan 31, 2013 at 9:58 PM, Merrick Christensen
merrick.christen...@gmail.com wrote:
I can
This is a problem with the Core Text renderer which can be worked
around by disabling it in the advance preferences.
The good news is that I know how to fix this problem. The bad news is
that it is a major undertaking and I have no idea when I'll have the
time it will take. :-(
Björn
On Wed
branch
is good news for those who wish to have a drawer. Merging it into
master does not seem like such an important step to me. Certainly not
compared with the issues I outlined above.
Björn
On Tue, Jan 15, 2013 at 3:54 PM, Bradford Smith fingerm...@gmail.com wrote:
It would be so lovely
On Fri, Dec 14, 2012 at 4:02 AM, philipmat wrote:
Just to clarify, `macmenu File.Print key=nop` works, it's the `nmap
D-P ...` part that doesn't.
Maps which involve D are case sensitive. You'll want to
nmap D-p C-p
instead, see :h cmd-key.
Björn
--
You received this message from
think it can be merged. If it is cleaned up so that
it works without having to put frameworks into /Sys/Lib/Fwk etc. then I'll
take a look at merging it.
Björn
--
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
as I can tell
(*p or Cmd+p).
Björn
--
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 information, visit http://www.vim.org/maillist.php
they are the same thing.
What do you really want to know?
Björn
--
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 information, visit http://www.vim.org/maillist.php
around and saw some forks
of PSMTabBarControl but they did not give me the impression that they
are what we need.)
I am also willing to financially support any sort of design / interface work
that falls in the above categories.
Thank you for offering!
Björn
--
You received this message from
On Sun, Nov 4, 2012 at 8:33 PM, George V. Reilly wrote:
Thanks, Bjorn. The CC=clang ./configure did the trick.
Perhaps https://github.com/b4winckler/macvim/wiki/Building
should be updated to point out that it also applies now to 10.7.
Sounds good. Would you mind doing that?
Thanks,
Björn
with clang. Try
make clean
CC=clang ./configure
make
If that doesn't work and you're not comfortable debugging build issues
I always recommend using the prebuilt binaries that I provide.
BTW, the MacVim repo is about 60 patches behind Vim.
Updated now. Thanks for the nudge.
Björn
--
You
squared off since MacVim is only drawing within views -- it
never tries to draw the window itself. Why would drawing inside a
view cause the window to be painted differently?
Björn
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply below the text you
on how to change
these (close/reopen window for changes to take effect).
Björn
--
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 information, visit http://www.vim.org/maillist.php
x 10.8.2 (Mountain Lion).
Does anyone know the solution to this problem?
I can confirm the problem. No fix at the moment but I've made a note of it.
Björn
--
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
)? If not, please try that and see
if it works.
Björn
[1] http://code.google.com/p/macvim/
--
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 information, visit http://www.vim.org/maillist.php
) on a philosophical level.
(Note that I do not particularly wish for somebody else to sign MacVim
for me or to upload MacVim to the App Store. If this is to happen
then I need to be able to control it myself.)
Björn
--
You received this message from the vim_mac maillist.
Do not top-post! Type your reply
it that way in order to keep things uniform and to avoid
hackery.
Björn
--
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 information, visit http://www.vim.org/maillist.php
Apple to log this at *runtime*
instead of as a compilation warning? I don't get it.
Björn
--
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 information, visit http://www.vim.org/maillist.php
~/.gvimrc file (create it if it
doesn't already exists):
macmenu File.Print key=nop
For more information see :h :macmenu and :h cmd-key.
Björn
--
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 information, visit
word...
Björn
--
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 information, visit http://www.vim.org/maillist.php
on the other hand looks uniform
across platforms. Another belated reason is that high-res displays
are becoming quite common (and of course now there are even Retina
displays). The NSTextView renderer struggles with these high
resolutions, whereas the Core Text renderer does not.
Björn
--
You received
I can do.
Björn
--
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 information, visit http://www.vim.org/maillist.php
the problem I instead switched back to building 32 bit
binaries.
Is there a reason why you need a 64 bit binary?
Björn
--
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 information, visit http://www.vim.org
be the right thing to do) or as a
temporary hack by editing src/auto/config.mk (easier). The latter
gets overwritten each time you run configure however...
Björn
--
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
not yet been implemented. So unfortunately the
only way to get it to work would be to implement gui_mch_flash()
inside gui_macvim.m.
Björn
--
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 information, visit
of MacVim.app on your hard
drive. This causes problems because Mac OS X happily opens any one of
them at random (even if they are buried deep inside a build
directory).
Search for MacVim.app and delete all app bundles except for the one
that you keep in /Applications.
Björn
--
You received
in console vim: it is not
built against the CG framework where the message seems to originate so
this is to be expected.
Björn
--
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 information, visit http://www.vim.org
1 - 100 of 679 matches
Mail list logo
