New tips March 2010
For each proposed new tip:
- Is it worth keeping as a separate tip?
- Should it be merged into an existing tip? Which?
- If it should be kept, is it ready for release? Which points need fixing? Should it be renamed?
Please edit this page (not the talk page) in the appropriate section below the following table.
Alternatively, comments can be posted on the mailing list.
| Proposed new tip | Current consensus |
|---|---|
| Build Python-enabled Vim on Windows with MinGW | - |
| Improved Javascript Indent script for Vim | - |
| Last position jump improved for Easy Vim | - |
| Project specific settings | - |
Please add your comment (sign with ~~~~) below the appropriate heading. Use ---- between comments.
General comments (not for a specific tip)
Build Python-enabled Vim on Windows with MinGW
See also
- Build Vim in Windows with Cygwin (MinGW is not very different)
- Compile a separate copy of Vim for Python coding (dodgy)
- Where to download Vim (including W32 binaries with Python etc.)
Merge (if deemed useful) otherwise delete? — Tonymec 19:42, March 30, 2010 (UTC)
I'm not sure about this at the moment. It has good content which needs to be kept, although like all the build tips it needs work. Re the point of the tip, I'm sure that it would be better and easy to find a Vim without Cream install to support the wanted version of Python, but proper info on building your own Vim needs to be on the wiki eventually. I have put all the "building Vim" tips I know of at Where to download Vim#Comments. I'll think some more later. JohnBeckett 10:32, May 20, 2010 (UTC)
Improved Javascript Indent script for Vim
There has been no progress towards developing this for inclusion with the Vim distribution, and that objective seems unlikely. This wiki is not the right place for scripts which are likely to remain undocumented and unmaintained (although we have some exceptions, notably CSV). While I think the right thing to do would be to delete (or possibly userfy) the page in order to avoid setting a precedent for future scripts that might be left here, nevertheless the script might be very useful so I propose that it be renamed and kept. I'm thinking of renaming it to "Javascript indent script" (although "JavaScript" might be more correct, and "indent file" is the commonly-used term) and keeping it. Any opinions? JohnBeckett 10:32, May 20, 2010 (UTC)
I agree this should be kept. This is reportedly resolving a deficiency with the current Vim distribution, not just adding a new feature.
I do think we need to somehow distinguish it from a "normal" tip, and provide some call for somebody to take over the maintenence, either on vim.org or as an official plugin. Maybe a new template is in order for such things?
--Fritzophrenic 14:46, May 20, 2010 (UTC)
Last position jump improved for Easy Vim
I have no idea what this is about but propose keeping the tip in view of its author. Perhaps Anwo will notice my confusion and add a short introduction saying why it's needed: what goes wrong if you do not use this tip? is the cursor slightly incorrectly restored? does that matter? does Vim crash? or what? JohnBeckett 10:32, May 20, 2010 (UTC)
Project specific settings
This is worth keeping. Change filetype based on directory path is vaguely related, but the two tips should probably develop separately. JohnBeckett 10:32, May 20, 2010 (UTC)
Agree. Probably make sure there's a See also note in each. --Fritzophrenic 14:47, May 20, 2010 (UTC)
Other solutions should be evoked in the tip page. I'm thinking about the plugins local_vimrc (there exists 3, may be 4 now, different implementations of the concept on SF), or plugin. They address exactly the same concern: having project-specific settings (actually, project does much more).
A side note about the necessity of using :help :setlocal, :help :map-local, etc. would be welcomed. --Luc Hermitte 12:36, June 3, 2010 (UTC)