Hi,

> I'd like to use Time Machine to retrieve an older .vimrc, but I don't see any
way to get Finder to show dot files. Is there a way?

Yes there is - you can use "tmutil" from the command line:

tmutil restore -v /Volumes/path-to-timemachine-backup/Users/username/.vimrc
~/vimrc

whereas "path-to-timemachine-backup" is the whole path including the date you
want to restore from.

The syntax of the "tmutil restore" follows the cp-command, so you can add a
couple of source files and restore it to the last parameter, which is the
target.

I hope this helps.


Frank

--
frank hellenkamp | interface designer
solmsstraße 7 | 10961 berlin

+49.30.49 78 20 70 | tel
+49.176.32 13 88 89 | mbl
+49.3212.100 35 22 | fax
jonas@...

http://depage.net | bureau
http://depagecms.net | content management
http://immerdasgleiche.de | read
http://everydayisexactlythesame.net | see
http://ideenkonserve.de | ideas

Hi Eric,

*ah*
And I forgot something...

>> I'd like to use Time Machine to retrieve an older .vimrc, but I don't see any
way to get Finder to show dot files. Is there a way?
>
> Yes there is - you can use "tmutil" from the command line:
>
> tmutil restore -v /Volumes/path-to-timemachine-backup/Users/username/.vimrc
~/vimrc

DON'T just copy the files with "cp", because then the extended-attributes that
timemachine uses will be copied along so you won't be able to edit these files
without removing these attributes and permissions first.


Best

Frank

--
frank hellenkamp | interface designer
solmsstraße 7 | 10961 berlin

+49.30.49 78 20 70 | tel
+49.176.32 13 88 89 | mbl
+49.3212.100 35 22 | fax
jonas@...

http://depage.net | bureau
http://depagecms.net | content management
http://immerdasgleiche.de | read
http://everydayisexactlythesame.net | see
http://ideenkonserve.de | ideas

On Jan 8, 8:07 am, björn <bjorn.winck...@...> wrote:
> On 8 January 2012 00:00, Bee wrote:
>
>
>
>
>
> > I have found a 'problem' with the highlight command in MacVim.
> > MacVim snapshot 53 -- osx 10.4.11
> > MacVim snapshot 60 -- osx 10.6.8
>
> > Neither one respects a gui highlight in .vimrc such as:
>
> > highlight Visual NONE ctermbg=Yellow ctermfg=Blue cterm=Bold
> > guibg=Yellow guifg=Blue gui=Bold
>
> > The same .vimrc works on MacOS with MacPorts gui vim-app 7.3.353 !
> > The same .vimrc works on WinXP with gvim 7.3.386 !
> > The same .vimrc works on Linux with gvim 7.3.372 !
>
> > Since I do not have Lion, and will not any time soon, I can not test
> > more a recent snapshot.
>
> > ** Will this be or has this been changed or fixed? **
>
> > I have added the gui highlight commands to .gvimrc and they work.
>
> > It is just more convenient for them to be in the same highlight
> > command.
>
> You 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 and sets its own
> custom color scheme.
>
> Björn


Hello Bjorn

I found a simple solution that works well for me.
I would like to request the feature added to MacVim.

I added a conditional to your $VIM/gvimrc

if !exists('default_colors')
   if !exists("colors_name")
     " Use the macvim color scheme by default
     colorscheme macvim
   endif
endif

And I added this line to my ~/.vimrc

let default_colors=1

Now MacVim does NOT clobber any of my settings,
BUT it will default to your setting!

Bill Muench
Santa Cruz, California

--
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 12 January 2012 20:20, Bee wrote:
>
> I found a simple solution that works well for me.
> I would like to request the feature added to MacVim.
>
> I added a conditional to your $VIM/gvimrc
>
> if !exists('default_colors')
>  if !exists("colors_name")
>    " Use the macvim color scheme by default
>    colorscheme macvim
>  endif
> endif
>
> And I added this line to my ~/.vimrc
>
> let default_colors=1
>
> Now MacVim does NOT clobber any of my settings,
> BUT it will default to your setting!

That sounds like 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 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 Jan 12, 11:10 pm, björn <bjorn.winck...@...> wrote:
> On 12 January 2012 20:20, Bee wrote:
>
>
>
>
>
>
>
> > I found a simple solution that works well for me.
> > I would like to request the feature added to MacVim.
>
> > I added a conditional to your $VIM/gvimrc
>
> > if !exists('default_colors')
> >  if !exists("colors_name")
> >    " Use the macvim color scheme by default
> >    colorscheme macvim
> >  endif
> > endif
>
> > And I added this line to my ~/.vimrc
>
> > let default_colors=1
>
> > Now MacVim does NOT clobber any of my settings,
> > BUT it will default to your setting!
>
> That sounds like 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

Thank you Björn.

I have added
let macvim_skip_colorscheme=1
to the .vimrc
I am now ready for the next snapshot.

Will there be any new snapshots for osx 10.6.8 Snow Leopard?

If not, I have edited your gvimrc to add the conditional and it works
fine.

Bill

--
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

Hi there -
      Wondering if there's a way to launch mvim from terminal without
it outputting errors / warnings and without it locking the process?
I'm not sure I have the terms right here so bear with me... basically,
when I do:

mvim /path/to/my/file

... from terminal, MacVim launches with my target file open... I see
some error / warning msgs in my terminal... and before I can continue
using terminal, I need to ctrl+c out.

Error output is fairly benign:

Invalid gemspec in [/usr/local/Cellar/ruby/1.9.3-p0/lib/ruby/gems/
1.9.1/specifications/heroku-2.8.4.gemspec]: invalid date format in
specification: "2011-09-23 00:00:00.000000000Z"
NERDTree: 3 invalid bookmarks were read. See :help
NERDTreeInvalidBookmarks for info.

Thanks in advance!
-matt

--
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... but even without errors, i'll still have to do the ctrl+c
thing to break out of whatever is locking up terminal

--
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 Wed, Jan 18, 2012 at 8:42 AM, busticated <itsbusticated@...> wrote:
> right... but even without errors, i'll still have to do the ctrl+c
> thing to break out of whatever is locking up terminal

Without the errors, mvim shouldn't lock up the terminal. At least it
doesn't on my machine.

c
--
Chris Lott <chris@...>

--
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 19 January 2012 10:21, Alex Lovell-Troy wrote:
> After some gentle prodding, I noticed that I need to build the Snow Leopard
> version of MacVim for general consumption.
>
> Sorry for the delay guys and here you go!
>
> https://github.com/alexlovelltroy/macvim/downloads

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 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 Thursday, January 19, 2012 at 1:13 PM, björn wrote:

On 19 January 2012 10:21, Alex Lovell-Troy wrote:

After some gentle prodding, I noticed that I need to build the Snow Leopard

version of MacVim for general consumption.

Sorry for the delay guys and here you go!

https://github.com/alexlovelltroy/macvim/downloads

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 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 19 January 2012 17:07, David Sanson wrote:
> I suspect this is impossible, given that it seems to be an issue with Lion's
> implementation of spaces rather than anything specific to MacVim. But it
> sure would be nice to able to use the keyboard to cycle to MacVim windows in
> other spaces, including those in their own native full-screen space. Has
> anyone figured out a way of doing this?
>
> With the mouse, a simple click on the dock icon cycles through all the
> windows in the all the spaces. But I don't know of any way to emulate this
> with the keyboard, and the Dock doesn't show up in full-screen mode. A bit
> more cumbersome, but keyboard only, is to use the shortcut for the
> "Application Windows" view in Mission Control (by default, assigned to F10,
> I think). From there, one can arrow around between open windows and recently
> opened documents. But this doesn't work in full-screen mode either.

I had a look at this and it turns out that it sort of already works to
cycle through windows in native full-screen.  The catch is that it
only works if you cycle to another window once before entering
full-screen.

It almost seems like a bug in Lion: if I enter and immediately exit
full-screen, then it is no longer possible to cycle to another window
(even though I'm out of full-screen).  If I click on another (MacVim-)
window when the current window is in this state, then I can cycle back
and everything 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 let this rest and ask that somebody else takes a look at 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

It would be really nice if we could implement it like how the Mac terminal App works. Command-`

Adding the Mac Vim mailing list.

On Thu, Jan 19, 2012 at 8:27 AM, Phil Dobbin <phildobbin@...> wrote:
> On 19/1/12 15:59, "Charles Campbell" <Charles.E.Campbell@...> wrote:
>> Phil Dobbin wrote:
>>> Hi, all.
>>>
>>> For the first time since I seriously started using Vim about six months ago
>>> I got this message on startup:
>>>
>>> `Vim: Caught deadly signal ABRT Vim: Finished. Abort trap`
>>>
>>> I'd been using it all day&  had just come back to it. This version of Vim
>>> (7.3 Included patches: 1-244, 246-353) is on OS X&  I compiled it myself
>>> back in December&  has worked fine. I subsequently got it back working by
>>> removing the FuzzyFinder plugin which I had recollections of reading about
>>> being troublesome some while ago but had since been fixed so whether this
>>> was a lucky guess or not I'm not sure. As an aside MacVim on the same
>>> machine worked fine when the terminal one wasn't working.
>>>
>>> Seeing as this is first problem I've had in this respect, can anyone advise
>>> on the best way to troubleshoot this kind of occurrence? I've Googled on it
>>> but nothing much came up. I've also got a copy of the crash log if that's
>>> any help to anybody.
>>>
>> * try to get a reproducible example; preferably with  vim -u NONE  .
>> Barring that, try to isolate to a minimal .vimrc and minimal qty of plugins.
>> * I'm not familiar with OS-X; under linux, I'd advise compiling with -g
>> and getting a core dump.  Find out where the crash occurred (file, line
>> number), and values of pertinent variables
>> * see if valgrind helps
>
> Hi, Chip.
>
> Thanks for the reply.
>
> The relevant part of the crash log as far as I can see is:
>
> `Exception Type:  EXC_CRASH (SIGABRT)
> Exception Codes: 0x0000000000000000, 0x0000000000000000
> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
>
> Application Specific Information:
> abort() called
>
> Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
> 0   libSystem.B.dylib                 0x00007fff891000b6 __kill + 10
> 1   vim                               0x00000001000df604 0x100000000 +
> 914948
> 2   libSystem.B.dylib                 0x00007fff891121ba _sigtramp + 26
> 3   libSystem.B.dylib                 0x00007fff891000b6 __kill + 10
> 4   libSystem.B.dylib                 0x00007fff891a09f6 abort + 83
> 5   libSystem.B.dylib                 0x00007fff890b8195 free + 128
> 6   dyld                              0x00007fff5fc06d5f`
>
> Going on what I could glean from that & what I read at:
>
> <http://www.gnu.org/s/libc/manual/html_node/Program-Error-Signals.html>
>
> is that Vim aborted before it crashed on launch. Starting Vim -u NONE it
> functioned as normal & upon removing a couple of plugins it reverted to
> normal.
>
> Modifying `libSystem.B.dylib 0x00007fff891000b6 __kill + 10` to make it a
> viable search term in Google/Stack Overflow turns up scores of entries of
> crashes across several different applications on OS X Snow Leopard (which is
> the OS this particular version of Vim of mine crashed on) so it may seem
> reasonable to  conjecture that this problem is OS specific. The odd thing
> however, is that the gui version MacVim functioned normally the whole time
> with the same plugins & vimrc.
>
> Cheers,
>
>    Phil...

--
/George V. Reilly  george@...  Twitter: @georgevreilly
http://www.georgevreilly.com/blog  http://blogs.cozi.com/tech

--
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 had a look at this and it turns out that it sort of already works to
cycle through windows in native full-screen.  The catch is that it
only works if you cycle to another window once before entering
full-screen.

It almost seems like a bug in Lion: if I enter and immediately exit
full-screen, then it is no longer possible to cycle to another window
(even though I'm out of full-screen).  

If I click on another (MacVim-)
window when the current window is in this state, then I can cycle back
and everything 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 let this rest and ask that somebody else takes a look at it.

It would be really nice if we could implement it like how the Mac terminal App works. Command-`

Hello Vim and iPad users,

If you have an iPad, you can now run Vim on it:

http://applidium.com/en/applications/vim/

Obviously not having a keyboard is a drawback, but otherwise it appears
to work well.

--
CART DRIVER: Bring out your dead!
LARGE MAN:   Here's one!
CART DRIVER: Ninepence.
BODY:        I'm not dead!
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

  /// Bram Moolenaar -- Bram@... -- 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

On 20/01/2012 11:43, Bram Moolenaar wrote:
>
> Hello Vim and iPad users,
>
> If you have an iPad, you can now run Vim on it:
>
> http://applidium.com/en/applications/vim/
>
> Obviously not having a keyboard is a drawback, but otherwise it appears
> to work well.
>

I've installed it on my iPhone & all seems OK. I already use iSSH on the
'phone with an Apple wireless keyboard but have yet had the time to try
it with Vim. Can't see why it wouldn't work too though.

Very cool 20th anniversary item.

Cheers,

     Phil...

--
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 Fri, Jan 20, 2012 at 2:43 AM, Bram Moolenaar <Bram@...> wrote:
>
> Hello Vim and iPad users,
>
> If you have an iPad, you can now run Vim on it:
>
> http://applidium.com/en/applications/vim/
>
> Obviously not having a keyboard is a drawback, but otherwise it appears
> to work well.

Wow, what a cool anniversary present. Vim on the iPad is something
I've been dreaming about for a while.

There's at least one immediate issue for me: if I launch vim with my
keyboard already on, the keyboard is non-functional until I turn it
off, wait for the on-screen keyboard to launch, then turn it back on
again. Obviously kind of a pain.

Of course, I assume it is impossible to install plugins?

c
--
Chris Lott <chris@...>

--
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 21 January 2012 05:56, dacresni wrote:
> I'm trying to build Clewn on snow leopard, has anyone else tried?

I made an effort to get it working a while ago and I summarized the
steps I took near the end of this thread:

http://groups.google.com/group/vim_mac/browse_thread/thread/1a7b591e69635357?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 information, visit http://www.vim.org/maillist.php

On 20 Jan 2012, at 16:34, Chris Lott wrote:

> On Fri, Jan 20, 2012 at 2:43 AM, Bram Moolenaar <Bram@...> wrote:
>>
>> <snip/>
>>
>> Obviously not having a keyboard is a drawback, but otherwise it appears
>> to work well.
>
> <snip/>
>
> There's at least one immediate issue for me: if I launch vim with my
> keyboard already on, the keyboard is non-functional until I turn it
> off, wait for the on-screen keyboard to launch, then turn it back on
> again. Obviously kind of a pain.

Yes, I had a similar experience, although maybe I'm missing something simple...
I found getting into visual (swipe across the screen) or insert  (press 'i')
mode easy enough, either with the on-screen keyboard, or with the apple wireless
keyboard connected, but I couldn't get out back into normal mode; there's no
sign of an 'esc' key on the on-screen, and it wasn't listening to the 'esc' key
on the wireless...

>
> Of course, I assume it is impossible to install plugins?

Or additional syntax files?

Regards, Andy

--
Andrew Long
andrew dot long at mac dot com