odern and properly maintained tab bar framework to
supersede PSMTabBarControl? (I had a look 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
> th
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?
T
y space" around the text view
inside the window. See ":h macvim-user-defaults" 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
.
Right now I'm confused as to how it can even be that the rounded edges
get "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 m
ing Vim with gcc and MacVim 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 n
ot; and it will now properly switch focus back to the netrw
> window.
>
> I'm using snapshot 65 on os 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 rec
e very much
> appreciated
Is this using snapshot 65 downloaded from the MacVim Google code page
[1] (i.e. the binary that I build)? 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" mailli
I try to mitigate the lack of automatic updates by tweeting
(@b4winckler) and posting here whenever I release a new snapshot.
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
I ports of Vim. It may look uglier but I think I'll
leave 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
icularly keen on asking for donations once a year just to pay the
Mac dev registration fee. Also, I'm not sure that I agree with
GateKeeper (and the App Store) 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
myself, which happens to be 10.8.
We already have one volunteer who builds snapshots for OS X 10.6. I
would now like to ask for help with building snapshots for 10.7. Who
is willing to help me with this?
Changes to this version can be found at [1].
Björn
[1] https://github.com/b4winckler/macvim
8b9a303f1234e745178fe08f6e
Honestly, what on earth would drive 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
-P ?
Try adding the following line to your ~/.gvimrc file (create it if it
doesn't already exists):
macmenu File.Print key=
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!
s of the start of said 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
than
before). The Core Text renderer 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
dly, then
I'll do my best to fix them, but that's all 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
o debug 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, vis
eaders are being used
(probably your custom version).
To get it to work you have to make it build and link the same Python
version. You can do this either by patching src/configure.in (which I
find to be a PITA but would be the right thing to do) or as a
temporary hack by editing src/auto/config.mk (e
guess is that this is a timing-related issue
since it is so hard to reproduce (by which I mean that I have never
been able to reproduce 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
work around?
This functionality has 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 reply
is also "true" vim --
just with a GUI added on top.
As for why it the message does not pop up 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" mai
instance of MacVim.
It sounds to me like you have two versions 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 excep
ainly works for me
and I use 'f' all the time). Try going 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 yo
le-gui=carbon to
configure (if you are unsure, then the answer is most likely that you
do NOT want to build the Carbon GUI and should instead build from the
sources at [1]).
Björn
[1] https://github.com/b4winckler/macvim
[2] https://github.com/b4winckler/macvim/wiki/Building
--
You received this m
endering decomposed UTF
- Vim expects filenames to be precomposed UTF: glob() does the right
thing by precomposing, ":!ls" does not precompose since filenames are
stored in decomposed form in the filesystem (and we should not /
cannot change this). If you are passing filenames to Vim (e.g
menu. The troubleshooting
guide may help you figure out which plugin it is:
https://github.com/b4winckler/macvim/wiki/Troubleshooting
...or let us know if that doesn't help.
Björn
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply bel
format
(decomposed form NFD) whereas for things to work they need to be in
normalization form C (some parts of the code uses routines in
Miscellaneous.h to do this conversion).
If it is only glob() needs to be patched, then it may be possible to
do the conversion to NFC to the relevant parts of the Vim
insight would be appreciated.
Hi,
I'm afraid I don't use zsh so can not really contribute at all to this
thread. Normally my response would be to ask on vim_use but this
really is specific to the Mac so I don't think you'll get much help
there.
Are there no zsh users o
Terminal Vim...it can be done
with the MacVim snapshot -- just call
"/Applications/MacVim.app/Contents/MacOS/Vim" from Terminal. That's
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
tunately not really much that I can do about this as it
would require substantial non-trivial changes to Vim itself.
> BTW thank Björn for the effort you put in MacVIm, it really rocks.
Cheers. Glad you like it!
Björn
--
You received this message from the "vim_mac" maillist.
Do n
; I am still getting separate windows.
I can just say the same as Tim: this preference works fine for me.
Maybe you should try going through the troubleshooting guide:
https://github.com/b4winckler/macvim/wiki/Troubleshooting
Björn
--
You received this message from the "vim_mac" m
scussion
titled "case insensitivity on hfsx" in the archives:
http://groups.google.com/group/vim_mac/browse_thread/thread/b2aa9fb761016205?pli=1
Björn
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply below the text you are repl
he definition of
'gui_mch_beep()' (in src/MacVim/gui_macvim.m). (Let me know how it
goes if you try.)
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
me somthing.
It works fine for me, which makes me thing that you are probably
entering the wrong path. For example, if you have a file "test.txt"
in your user folder "/Users/yourname" then the correct incantation is
mvim://open?url=file:///Users/yourname/test.txt
Björn
--
Y
f memory serves me correctly). If not, message me personally
and we'll sort it out.
I might release a new snapshot in the coming days, so I don't think it
necessary to build a new version just yet (unless you want to, of
course).
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
e to wait until I release a new snapshot.
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
t go-=T
For more information, see ":h 'go".
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
indow?
It sounds to me like you've accidentally downloaded the *very
outdated* Carbon port of gvim. Go to
http://code.google.com/p/macvim/
and download the latest snapshot of MacVim.app.
Björn
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type y
ut somewhere in your path), then you can do
mvim -u NONE
Otherwise, try
/Applications/MacVim.app/Contents/MacOS/Vim -g -u NONE
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
thout any problems (I tried ':nnoremap gA :echo
"hi"') which makes me think one of your plugins or rc-files are
interfering. Try going through [1] to figure out where the problem
is.
Björn
[1] https://github.com/b4winckler/macvim/wiki/Troubleshooting
--
You received this me
"mvim -v" or (if
you don't have the mvim script)
/Applications/MacVim.app/Contents/MacOS/Vim
If this version doesn't work, then the problem is with core Vim in
which case I would ask that you please report to the vim_dev Google
group instead.
Björn
[1] https://github.com/b4win
om glob()) is:
>
> <ö> 246, Hex 00f6, Octal 366
This has to do with Unicode normalization [1]. The output from !ls is
not composed, whereas when you paste it in Vim it is composed. The
problem arises because you are piping characters from an external
command.
I suppose we
hat I'd suggest you start by disabling all your plugins and
then re-enabling them one at a time until you find out which one is
causing you grief (assuming the freeze doesn't happen with no
plugins).
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
with --remote by putting a + in front of it. Something like
this should serve your purposes:
mvim --remote-tab-silent +999 filename
(This will put the cursor on line 999 [or the last line if the file is
shorter than that] -- you can't leave the number out to go to the last
line however.)
B
en fails
> to display the file. Any pointers?
Have you by any chance replaced the system Python or any other library?
What happens if you try starting from Terminal? (You can also check
to see if there are any errors being logged to console by opening
Console.app.)
Björn
--
You received this
heights. Try going in to
the advanced preferences, enable the experimental renderer and
restart. The experimental renderer keeps line heights fixed so it
should not suffer from the problem you are describing.
Björn
--
You received this message from the "vim_mac" maillist.
Do not top-post!
he archives.
The short answer is: it will require a lot of work to implement
because MacVim cannot make use of the NSScrollView class, but I also
think it would be nice to have.
Björn
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply below the t
xim -xsmp
> -xterm_clipboard -xterm_save
> system vimrc file: "$VIM/vimrc"
> user vimrc file: "$HOME/.vimrc"
> user exrc file: "$HOME/.exrc"
> fall-back for $VIM: "/usr/share/vim"
> Compilation: gcc -c -I. -D_FORTIFY_SOURCE=0 -Ipro
On 25 January 2012 09:47, björn wrote:
> On 18 January 2012 20:20, Stanislaw Pusep wrote:
>> The subject says everything, a few remarks:
>>
>> 1) It's NOT a SuperTab fault; Ctrl-N/Ctrl-P is slow also! However, it's
>> easier for me to refer to the whole con
l-C, variable name completes
> instantly;
> 7) Non-Perl (SQL, for instance) source completion is fast.
>
> Any clues on how to debug this?
I can reproduce and I think I know what the problem is. I'll see what
I can do about it.
Björn
--
You received this message from the &qu
On 22 January 2012 19:44, Patrick Donelan wrote:
> Just checking the status of this - is it still unimplemented?
It has not been implemented -- I'll leave it to somebody who wants
this feature to implement it and send me a patch.
Björn
--
You received this message from the "vim_
SCPlugin authors on their mailing list
but as far as I can tell that project has not been updated since the
beginning of 2010, so it seems unlikely that this bug will be fixed
soon.
Björn
[1] https://github.com/quicksilver/Quicksilver/issues/619
--
You received this message from the "vi
69635357?pli=1
As far as I can tell from that thread, I did manage to get it up and
running but there were some problems I never resolved.
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 infor
verything works (even in full-screen).
I've tried to work around this bug by setting
NSWindowCollectionBehaviorParticipatesInCycle at various places in the
code, but no luck so far. Not really sure what to do about it, but it
seems that some hack is in order to get this working.
I'll l
Thanks to Alex for making his build available.
I'd appreciate if some of you with Snow Leopard can try this out and
let me know that it works, since this is the first build Alex has
made. Once I get some confirmations I'll update the Google code page
and tweet about it etc.
Björn
--
You re
e a reasonable solution. I have pushed a patch which
will skip loading the macvim color scheme if you add the line
let macvim_skip_colorscheme=1
to your ~/.vimrc (note that it will NOT work if you put that in your ~/.gvimrc).
Thanks for the suggestion,
Björn
--
You received this messag
should be able to work around this issue by adding the line
let colors_name = "mine"
to your ~/.vimrc file (substitute "mine" for whatever you like).
The reason why you have to do this is that if colors_name is not set
MacVim assumes the color scheme hasn't been modified an
ences the Core Text renderer is used. If not, it uses the
NSTextView-based renderer.
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
2012/1/2 Tony Mechelynck:
> I'm redirecting this thread to the vim_mac group and adding Björn to the CC.
Thanks for bringing this to my attention Tony.
> On 02/01/12 03:33, Zhao Cai wrote:
>>>
>>> On 01/01/12 16:37, Zhao Cai wrote:
>>>>
>>>
uggest you update.
Björn
[1] https://github.com/b4winckler/macvim/wiki/ChangeLog
--
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
will MacVim lunch Vim as a helper to do the cross-platform task as
> it do like in Windows and Linux?
Take a look at
https://github.com/b4winckler/macvim/blob/master/src/MacVim/README
It describes the overall design of MacVim and also says something
about the layout of the source code.
Bjö
f time so let me
emphasize that i am _thinking_ about it, I've not actually started,
nor may I ever start.
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
and then perhaps setting your color scheme 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
build 53, then
you can read the latest help file at [1]. Just search for "cmd-key".
Björn
[1] https://github.com/b4winckler/macvim/blob/master/runtime/doc/gui_mac.txt
--
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 10 December 2011 18:56, dado wrote:
> I tried
> :h cmd-key
> and got
> E149: Sorry, no help for cmd-key
You must either have a very old version of MacVim, or you're not
running MacVim at all. Get the latest version from:
http://code.google.com/p/macvim/
Björn
--
You rece
amount of space. Take a look at
:h macvim-user-defaults
You will want to change the various MMTextInset* user defaults.
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
with a new file), my .vimrc seems not to be used anymore.
>
> Does this make more sense?
Hmm, to be honest, no. The same code path are used in all of these cases.
Just out of curiosity -- does it work if you put your customizations
in ~/.gvimrc instead?
Björn
--
You received this message f
On 4 December 2011 13:52, Federico Calboli wrote:
> On Dec 2, 5:12 pm, björn wrote:
>> On 1 December 2011 13:29, Federico Calboli wrote:
>>
>> Does the font contain weird characters or spaces?
>
> not to the best of my knowledge, though the font is very much an alp
These maps should do:
> map :tabnext
> map :tabprevious
> map :tabedit %
> map :bwipeout :tabclose
>
> The problem is that when I open vim, set these maps and then do a cmd-
> t it will not work. Neither with e.g. map :echo LOL.
These shortcuts are bound to menus so you ha
a facelift.
In the meantime, the best idea would be to publish step-by-step
instructions on how to get your redesigned icon and replace the
default icon. You are welcome to add a page to the MacVim wiki [1].
Björn
[1] https://github.com/b4winckler/macvim/wiki
--
You received this message from the
open first MacVim and then the file (with "File - Open"
> or CMD-O).
>
> Do you have any advice what could I do in order to have the .vimrc
> used with "Open with..." too?
It should always source the ~/.vimrc. What steps did you take in
order to come to the conclu
u call "set gfn=fontname"?
Does the font contain weird characters or spaces? Maybe the code is
not properly escaping something. If I had the font I'd try it out,
but I'd rather avoid having to write and ask for a copy of the font.
Björn
--
You received this message from the &q
focus and hence the blinking would not change when you put a
window in the background.
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
l I know is that a single, boolean, "macmeta" option won't be enough. I
> think we have to implement another option to define which key(s) should work
> as "Meta" instead of "Option" but I understood that you didn't want to have
> that kind of stuf
-site-lib-vim
>
> What is actually going on in this case? Is there an easy fix to this
> problem?
Try opening the advanced preferences and toggle the option for "use
experimental renderer". I'm guessing the problems go away if you
enable the experimental renderer? (It is
o do
> it.
I never received a patch, so no, it has not been implemented (I will
not implement this myself since I have no use for it and my impression
was that not too many people were asking for it).
Still waiting ...
Björn
--
You received this message from the "vim_mac" mail
t my
attention, but I've been moving houses so your first post fell through
the cracks. It is good that you reminded me.
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
62).
In that case I suggest that you do a "make clean" and then call "make" again.
If that doesn't work try downloading a snapshot (currently snapshot 62
if you are using Snow Leopard, note that there is one for Lion and one
for Snow Leopard) and see how that goes.
Björn
--
Are you now saying that you are actually using 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
any help !
I'm unsure which version of Vim you are using. You mention pressing
Cmd+q so I'll assume it is some version of MacVim? What version (look
under the menu MacVim -> About) and where did you download it from if
so? Or did you build from sources?
Björn
--
You received thi
rd bug reports and unnecessarily waste time trying
to help people to get MacVim working again. :-O
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
This is a problem that only occurs when building 64 bit
and for that reason this snapshot is 32 bit. Are there any downsides
to running MacVim 32 bit? Not that I know of.
(Also, there was a bug with the 'colorcolumn' option crashing Vim and
the patch for this is included in this bui
e file in terminal by command "mvim"
> Any ideas?
Can you outline some steps on how to reproduce the problem? (I've
never come across this problem myself.)
You can try troubleshooting the problem yourself by going through [1].
Björn
[1] https://github.com/b4winckler/macvim/wik
wn). I posted to vim_dev (hoping somebody who worked on
the Python interface would answer) but got nothing.
Any help with getting Python not to crash would be appreciated. Has
anybody on this list any experience with embedding Python?
Björn
[1] http://code.google.com/p/macvim/issues/detail?id=3
omized NSMenuItem class but I have not attempted to implement this
myself. (Patches are welcome, of course.)
Note though that if you hover the mouse over a menu item for a couple
of seconds a tooltip will pop up displaying the command.
Björn
--
You received this message from the "vim_mac&quo
been wanting to write a "Vim view"
framework for a while now but have yet to find the time for this (it
would require a lot of work). Hopefully I'll get around to this some
time...and the more people who want it, the more motivation I have to
get started. ;-)
Björn
--
You received
searches for the word
that was selected in Chrome.
Note that Cmd+g and "n" in MacVim are not the same, see ":h macvim-find".
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
it works fine for me. Also note that in order
for it to work you have to enter full-screen by using the menu, or by
pressing the shortcut for the menu (which should be Cmd+Ctrl+f unless
you are using an old version of MacVim).
Björn
--
You received this message from the "vim_mac" mai
ess 'y'
> ~/.vim/plugin/myscript.vim
> will be copied into the % register.
>
> How then to copy it to the system clipboard?
I add the line
set go+=A
to my ~/.gvimrc. This means that the "modeless selection" is
automatically copied on selection (see ":h 'go
st MacVim snapshot supports Lion native full-screen. (I
believe that is what the OP was asking for?)
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
unless_ you specify the
--with-macsdk flag is passed to configure, see [1]. You do need the
very latest commit however.
Björn
[1] http://code.google.com/p/macvim/issues/detail?id=375
--
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
2011/9/22 Nikola Knežević:
> On 18 Sep 2011, at 16:32 , björn wrote:
>
>>
>> I would like to not have to maintain a build for Snow Leopard. If you
>> want to help out and maintain a build for legacy systems please write
>> to me directly and I'll send you my
out and maintain a build for legacy systems please write
to me directly and I'll send you my build script.
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
t I will ever merge it with mainline. Sorry.
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
if
> PERLSITELIB/ExtUtils/xsubpp doesn't exist. If you find any value in it, let
> me know.
Thanks for the patch.
So, if I build against the default Perl version this patch has no
effect? If it doesn't have any negative side effects for people
without a custom Perl, then I don&
o blame.
If you still can't figure out what is wrong, you really need to give
us more details about your setup.
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
which is a pain.
If anybody has any tips / examples on how to do the Lion-style
scrollers without NSScrollView please let me 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 informa
ed at [1] to build the
official binaries.
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
de works. If you disable the
experimental renderer the problem you are having probably goes away
(of course, the default renderer is much slower so it is not something
I'd recommend).
It would not be easy to fix this problem in a non-hacky way (meaning,
you will have to live with it for
ossible_ to implement this differently, but
its not something I'm particularly interested in doing so this will
only happen if somebody else sends me a patch (it won't be trivial to
implement).
Björn
--
You received this message from the "vim_mac" maillist.
Do not top-pos
101 - 200 of 1073 matches
Mail list logo
