Re: Vim 7.4a ready for beta testing
On Mon, Jul 8, 2013 at 4:42 PM, björn 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 you off). Even on Snow Leopard build there are some glitches here, but nothing that makes MacVim unusable (it's just on resizing). But with Core Renderer enabled it's unusable for Japanese text (Japanese characters are larger, so they pile up, but with CR disabled it does proper spacing). Since I use it for Japanese just once in a while, I left it with CR enabled for day to day programming. > As for not being able to enter full screen: I do not have access to a Lion machine to try on. But to rule out problems with Douglas' build, please try running the binary I built for 10.6. On second thought - it does not support Lion-native full screen, so that may be somewhat pointless. Maybe try disabling native full-screen in the prefs and see if that works. I didn't have the fullscreen issue, so I couldn't test that. -- Douglas Drumond -- -- 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. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: macvim OS X 10.9 Mavericks build
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 MAC_OS_X_VERSION_MAX_ALLOWED requires > > > > > AvailabilityMacros.h to be defined. This diff is all that's required > upstream, the rest is brew specific: > > > > > > > > > > diff --git a/src/os_unix.c b/src/os_unix.c > > > > > index bb4c10e..00d9728 100644 > > > > > --- a/src/os_unix.c > > > > > +++ b/src/os_unix.c > > > > > @@ -18,6 +18,10 @@ > > > > > * changed beyond recognition. > > > > > */ > > > > > > > > > > +#if defined(__APPLE__) > > > > > +#include > > > > > +#endif > > > > > + > > > > > /* > > > > > * Some systems have a prototype for select() that has (int *) > instead of > > > > > * (fd_set *), which is wrong. This define removes that prototype. We > define > > > > > > > > > > -- > > > > > -- > > > > > > > > Thanks for the patch. > > > > > > > > What is the reason that we have to pollute os_unix.c (which has > > > > nothing to do with OS X) with an OS X-only header? > > > > > > > > What exact problem does this patch address and is there perhaps a > > > > better way to solve it? > > > > > > > > Björn > > I agree -- this was just the patch located at the bottom of the pull > request on the homebrew issue tracker. Vim builds if you place the #include > in os_mac.h > > On Friday, June 28, 2013 5:05:03 PM UTC-4, Bram Moolenaar wrote: > > Jimmy Zelinskie wrote: > > > > > > > > > As per the discussion at > https://github.com/mxcl/homebrew/pull/20831#discussion_r4917643 > > > > > > > > > > The required macro MAC_OS_X_VERSION_MAX_ALLOWED requires > > > > > AvailabilityMacros.h to be defined. This diff is all that's required > upstream, the rest is brew specific: > > > > > > > > > > diff --git a/src/os_unix.c b/src/os_unix.c > > > > > index bb4c10e..00d9728 100644 > > > > > --- a/src/os_unix.c > > > > > +++ b/src/os_unix.c > > > > > @@ -18,6 +18,10 @@ > > > > > * changed beyond recognition. > > > > > */ > > > > > > > > > > +#if defined(__APPLE__) > > > > > +#include > > > > > +#endif > > > > > + > > > > > /* > > > > > * Some systems have a prototype for select() that has (int *) > instead of > > > > > * (fd_set *), which is wrong. This define removes that prototype. We > define > > > > > > > > So, on what systems is AvailabilityMacros.h available? > > > > > > > > Isn't this a chicken-egg problem? > > > > > > > > -- > > > > Veni, Vidi, Video -- I came, I saw, I taped what I saw. > > > > > > > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net > \\\ > > > > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/\\\ > > > > \\\ an exciting new programming language -- http://www.Zimbu.org > /// > > > > \\\help me help AIDS victims -- http://ICCF-Holland.org > /// > > This documentation[1] leads me to believe that OSX 10.2+ supports it. This > homebrew pull request[2] cites that it has been built successfully on > 10.8.4-x86_64 and 10.7.5-i386. > > [1] > http://wiki.herzbube.ch/index.php/Mac_OS_X_Programming#Availability_Macros > [2] https://github.com/mxcl/homebrew/pull/20473#issuecomment-19434950 > Usually the AvailabilityMacros.h header gets included when you pull in a Carbon/Cocoa header - it would be good to know why this is problem is showing up on 10.9 but nowhere else (or does it?). On the other hand, placing the include at the top of os_mac.h should be harmless as this header should be present when building on a Mac. At the moment I don't think it is urgent to patch this, since 10.9 has not yet been publicly released, but if somebody with access to 10.9 took a closer look it would certainly be helpful (as I probably won't get 10.9 myself for a long time). 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. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim 7.4a ready for beta testing
On Sun, Jul 7, 2013 at 10:39 PM, Douglas Drumond wrote: > > On Sun, Jul 7, 2013 at 1:13 PM, peiman khosravi wrote: > > > > Also, I tried to resize the window by dragging the right edge and this > happened (attached). > > > > I was not able to reproduce fullscreen issue here, but I could see the > glitch from 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? [1]), I'll see what I can do. > I have tried very hard to avoid these types of display bugs, but unfortunately it is unavoidable without some form of double buffering which I have not (yet) implemented for the Core Text renderer due to speed (and memory) concerns. 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 you off). As for not being able to enter full screen: I do not have access to a Lion machine to try on. But to rule out problems with Douglas' build, please try running the binary I built for 10.6. On second thought - it does not support Lion-native full screen, so that may be somewhat pointless. Maybe try disabling native full-screen in the prefs 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 Groups "vim_mac" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: terminal command to open multiple files in a vim split screen instance
On 7 Jul 2013, at 21:14, Johann Bestowrous wrote: > I was wondering if there was a terminal command that would let me open a set > of files in a split screen with MacVim. I let my lazy imagination run wild on > Sundays and accomplishing this would give my inner sloth serenity when > working with a couple of different frameworks. This opens files in horizontal splits: $ mvim -o foo.txt bar.txt baz.txt And this opens them in vertical splits: $ mvim -O foo.txt bar.txt baz.txt I found this out via `mvim -h` :) Yours, Andy Stewart -- -- 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. To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
