Thursday, January 31, 2013

Re: Updating Syntax menu

So, would this imply that the Syntax menu should only be updated when a new version is compiled?

I hink i'm going to keep a copy of the files i updated, probably putting them in the directory that does not get changed, along with a README, for myself, to remind me how to update this file.

Thanks,

Russ

> Hm, after some more searching, I could find no "makemenu.vim" at any
> 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
> run-time use.
>
> I suppose you might create an unnamed branch in your hg clone, with your
> modified runtime/makemenu.vim, and then use
>
> cd src
> # source any script to set config settings
> make menu
>
> to generate the menu.
>
> See also
> hg help branch
> http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
>
> 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.
>
>
> Best regards,
> Tony.
> --
> "Even if you're on the right track, you'll get run over if you just sit
> there."
> -- 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
>
>
>

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments: