Re: MacVim snapshot 72 for OS X 10.9 (on 10.5 and 10.6)
Am 26.10.2013 um 20:54 schrieb björn: I had another look and managed to avoid using deprecated CGContext.. functions. Check the latest commit in the repo. I build this version on 10.6.8 and it compiles and seems to work fine. (I’m using the Core Text renderer.) Building on 10.5.8 (PPC) failed with: cp -pR MacVim-*.icns /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/ ** BUILD FAILED ** The following build commands failed: PSMTabBarControlFramework: CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/AquaTabClose_Front_Pressed.tif images/AquaTabClose_Front_Pressed.tif On 10.6.8 I have TIFF Files, on 10.5.8 I only have PNG Files CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/AquaTabClose_Front_Rollover.tif images/AquaTabClose_Front_Rollover.tif CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/AquaTabClose_Front.tif images/AquaTabClose_Front.tif CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/TabIcon.tif images/TabIcon.tif CopyTiffFile /Volumes/Diotima/src/macvim/src/MacVim/PSMTabBarControl/../build/Release/PSMTabBarControl.framework/Versions/A/Resources/TabControlRep.tif images/TabControlRep.tif MacVim: CopyStringsFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/English.lproj/InfoPlist.strings English.lproj/InfoPlist.strings CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/Colors.plist Colors.plist CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/Actions.plist Actions.plist CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/SystemColors.plist SystemColors.plist CopyPlistFile /Volumes/Diotima/src/macvim/src/MacVim/build/Release/MacVim.app/Contents/Resources/KeyBinding.plist KeyBinding.plist (10 failures) To be sure I re-cloned the repository but the failures remain. When I copy the files manually (taking the tiffs from the 10.6.8 machine) I get a working Vim. On 10.5.8 I have Python 2.5.1, on 10.6.8 I have Python 2.6.1, in case that matters. Axel -- -- 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.
ImportError: No module named site
I recently started using jedi. So far I installed it on 2 linux system without any problem but I got stuck to using it on os x. I followed this instructions http://redkrieg.com/2012/12/11/writing-python-like-a-jedi/. when I try to use vim I am getting: mtest.py [New File]ImportError: No module named site and after that I can not quit the vim and I have to close the terminal. I dont know what exactly could be the problem. I recently upgrade to maverick and also I use Enthought Canopy for managing my python package which it changes the default python path. Also: :messages = Messages maintainer: Bram Moolenaar b...@vim.org :ver http://pastebin.com/fF9KpVeW :omnifunc omnifunc= :python import sys; sys.version [No Name] 0,0-1 All ImportError: No module named site :scriptnames http://pastebin.com/TpgjCpdL ~/.vimrc execute pathogen#infect() syntax on filetype plugin indent on let g:SuperTabDefaultCompletionType = context let g:jedi#popup_on_dot = 0 /usr/share/vim http://pastebin.com/Wa1yXT9z Any idea? Thanks -- -- 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.
[New File]ImportError: No module named site
I recently started using jedi. So far I installed it on 2 linux system without any problem but I got stuck to using it on os x. I followed this instructions http://redkrieg.com/2012/12/11/writing-python-like-a-jedi/. when I try to use vim I am getting: mtest.py [New File]ImportError: No module named site and after that I can not quit the vim and I have to close the terminal. I dont know what exactly could be the problem. I recently upgrade to maverick and also I use Enthought Canopy for managing my python package which it changes the default python path. :messages = Messages maintainer: Bram Moolenaar b...@vim.org :ver http://pastebin.com/fF9KpVeW :omnifunc omnifunc= :python import sys; sys.version [No Name] 0,0-1 All ImportError: No module named site :scriptnames http://pastebin.com/TpgjCpdL ~/.vimrc execute pathogen#infect() syntax on filetype plugin indent on let g:SuperTabDefaultCompletionType = context let g:jedi#popup_on_dot = 0 /usr/share/vim http://pastebin.com/Wa1yXT9z Any idea? Thanks -- -- 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: wildignore and opening files
On Saturday, October 26, 2013 12:15:46 PM UTC+2, Martin Finke wrote: Setting wildignore seems to make it impossible to open ignored files at all...for example, let's say we're ignoring the pattern: *.min.js because we don't want minified files to turn up in searches and when using :e. With this pattern ignored, it's not possible to open a file like jquery.min.js, even when double-clicking in Finder or dragging the file onto the MacVim window. It will just show an error E479: No match. Is there a way to solve this? 'wildignore' ignores files matching the pattern when using |wildcards| in Ex-commands that take a filename, or in expand(), glob() and globpath(). You can always open the file by typing its full name without wildcards, e.g. :e jquery.min.js or by clicking it (or hitting o) in a netrw window (after editing a directory). Best regards, Tony. -- signal(i, SIG_DFL); /* crunch, crunch, crunch */ -- Larry Wall in doarg.c from the perl source code -- -- 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: Support Mac resume feature
On Friday, October 25, 2013 8:39:40 PM UTC+2, björn wrote: On Thu, Oct 24, 2013 at 5:35 PM, wrote: 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 buffers, tabs that I have opened in macvim could be resume if I accidentally quit the app. This has been requested before. That functionality can be mimicked from within vim by using various options and perhaps autocommands for some special occasions. Start by looking at :help autowriteall, which should do what you want for the case of accidental closure. For automatic reopening of windows, look at :h sessions, which would almost certainly work much better wrt to Vim than Apple's version anyway. I sure hope the Apple implementation of this doesn't get put into MacVim. Yeah, I think the consensus was that Apple's implementation is inferior in the case of Vim. That being said. Configuring Vim to autosave documents probably requires a PhD in Vim script, whereas the resume feature in other apps is automatic. It would be nice to have something in MacVim that was as easy to use. Björn You could use :au VimLeave mks! then create a desktop shortcut to start Vim with the -S switch, which hardly requires a PhD in Vim scripting. It does assume that your Vim executable has been compiled with +autocmd and +mksession. The only problem AFAIK would be which value to set for 'sessionoptions' (q.v.) to get all you need and avoid unneeded duplication of code with, for instance, your vimrc. Or if (like me) you want to start Vim almost every time with the same files in the same windows and tabs, you could write a session script manually, with whatever ex-commands you would like to see Vim run after sourcing your vimrc, in order to load your usual session, bypassing :mksession entirely. The reason you might want to keep these commands out of your vimrc would ve so that you could run Vim from time to time with no saved session. See :help :version :help VimLeave :help :mksession :help -S :help 21.4 :help views-sessions :help 'sessionoptions' Best regards, Tony. -- With a gentleman I try to be a gentleman and a half, and with a fraud I try to be a fraud and a half. -- Otto von Bismark -- -- 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
Björn wrote: 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 that AvailabilityMacros.h is available on all versions of OS X, because it's copyright header states 2001-20xx which matches the OS X 10.0 release timeline. Is the os_mac.h code also targeting OS 9? In that case we should add a configure check. Yes, pre-OS X should be supported. If there is a suitable #ifdef check for that, then it should be possible to submit as a patch to mainline Vim. OK, I've updated the patch with a configure check: https://gist.github.com/felixbuenemann/6150257 This looks good to me ... but should we perhaps be checking for Availability.h instead as that is what is used on Mavericks (and earlier OS X versions did not need explicit inclusion of AvailabilityMacros.h)? The macros used in the vim codebase are defined in AvailabilityMacros.h not Availability.h. Availability.h has similar but not the same macros, so using it would require cluttering the code with even more ifdefs. OK. Well, then I think this solves the problem of compiling on OS X 10.9 neatly and that it could be included in mainline Vim. Bram, can you please consider this patch for inclusion. It should apply cleanly (I just tried myself) and it automatically solves the problem of us having to know exactly when this header was made available. I've pasted it below for your convenience. Note that Felix Bünemann wrote the patch, not me. Thanks, I'll put it in the todo list. How about the patch that Kazunobu Kuriyama sent on Friday? -- I wonder, do vegetarians eat fruit bats? /// 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/// -- -- 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 snapshot 72 for OS X 10.9
On Sun, Oct 27, 2013 at 1:25 AM, Douglas Drumond drumond.doug...@gmail.com wrote: Newer versions won't work in older Macs and cross-compiling is too much of a hassle because of different python and ruby versions. I assume this is related to Vim, not MacVim? Apple does make it ease for the developers to compile apps that run on all the different versions of OS X. You just need to setup your build parameters properly and make sure to properly use the APIs unavailable in previous versions of the OS. -- Janusz Bossy -- -- 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 snapshot 72 for OS X 10.9
On Oct 27, 2013, at 11:25 AM, Janusz Bossy janusz.bo...@gmail.com wrote: On Sun, Oct 27, 2013 at 1:25 AM, Douglas Drumond drumond.doug...@gmail.com wrote: Newer versions won't work in older Macs and cross-compiling is too much of a hassle because of different python and ruby versions. I assume this is related to Vim, not MacVim? Apple does make it ease for the developers to compile apps that run on all the different versions of OS X. You just need to setup your build parameters properly and make sure to properly use the APIs unavailable in previous versions of the OS. Unlike most other apps, MacVim links to the Apple-supplied versions of Perl, Python, and Ruby, which are something of a moving target between major OS versions. If you could demonstrate a way of avoiding this hassle, I'm sure Björn (and others) would be quite interested. Cheers, Carl -- -- 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.
