search

rzyns / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

Vim runtime files out of date; smartindent disabled #332

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. set ai si
2. Paste text

What is the expected output? What do you see instead?

I expect the text to be indented intelligently. Instead, no indentation occurs.

What version of MacVim and OS X are you using (see "MacVim->About MacVim"
and  "Apple Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6
Intel")?

MacVim Snapshot 57.

Please provide any additional information below.

I disabled the configuration files one by one until I discovered the culprit: 
menu.vim (<MacVim.app>/Contents/Resources/vim/runtime/menu.vim).

Renaming the file fixed the problem, but then I realised the entire runtime 
directory is out of date. Replacing it with the latest one from vim.org 
resolves the issue. This directory should be kept in sync with new Vim releases.

Original issue reported on code.google.com by mebad...@gmail.com on 14 May 2011 at 12:43

GoogleCodeExporter commented 9 years ago 
A few more points:

- I'm running Mac OS X 10.6.6

- Even if smartindent is not set, the text should still be indented based on 
the filetype. This doesn't happen.

- Updating the runtime directory removes the Mac customisations in the menu 
(for eg, CMD-T to open a new tab). This makes the resolution more complex than 
just updating the directory.

Original comment by mebad...@gmail.com on 14 May 2011 at 1:23

GoogleCodeExporter commented 9 years ago 
There have been discussions about the paste behavior on vim_use recently, 
please add your comments to one of the threads there (there is one that I 
started, for example).  If you want more control over how indentation is 
handled during a paste you need to look at the <C-R> commands, see ":h 
i_CTRL-R".

The runtime files are updated every now and then but you will have to build 
from source yourself to get them.

These issues are not bugs in MacVim specifically, if you have anything more to 
add then please take this discussion to vim_use.

Original comment by bjorn.winckler@gmail.com on 15 May 2011 at 3:07