135759Re: Updating Syntax menu
- Jan 26, 2013On 26/01/13 15:34, Russell Urquhart wrote:
> On Sat, Jan 26, 2013 at 06:21:45AM +0100, Tony Mechelynck wrote:Hm, after some more searching, I could find no "makemenu.vim" at any
>> As has repeatedly been said on this list, you should NEVER change
>> anything in the $VIMRUNTIME tree because any update can do away with
>> your changes, without telling you that it did. You should rather save
>> the modified version of makemenu.vim as $VIM/vimfiles/makemenu.vim
>> (system-wide on any platform) or ~/.vim/makemenu.vim (single-user on
>> Unix-like systems) or ~/vimfiles/makemenu.vim (single-user on Windows).
>> Best regards,
>> Why don't elephants eat penguins ?
>> Because they can't get the wrappers off ...
> Hi Tony,
> Yes you are correct, i will update my user makemenu.vim accordingly. I, while i was doing this, was thinking the same thing, what do i do, if/when i update my vim. And this will work, right, because i will source THIS makemenu.vim, rather than the system wide one, right?
> Thanks for steering me in the right direction!
depth under $VIMRUNTIME in the Vim distribution. Where I see it is in
the source, at ./runtime/makemenu.vim, and it says it is used by "make
menu" in the src directory, which implies a compile-time rather than
I suppose you might create an unnamed branch in your hg clone, with your
modified runtime/makemenu.vim, and then use
# source any script to set config settings
to generate the menu.
hg help branch
The above assumes a Unix-like OS. I'm not sure which differences (if
any) would be required to generate the menus on Windows. It may or may
not depend on which compiler you use to compile Vim.
"Even if you're on the right track, you'll get run over if you just sit
-- Will Rogers
You received this message from the "vim_use" 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
- << Previous post in topic Next post in topic >>