New tips February 2008
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 | Link | Current consensus |
|---|---|---|
| Automatically add Python paths to Vim path | discuss | Keep |
| Substitute Word Under Cursor | discuss | Merged to VimTip464 |
| VirtualStore | discuss | Merged to VimTip1542 |
Note 1 All content from the "plugin" tips has been copied to a new "Best plugins" section on the Vim scripts page.
Please add your comment (sign with --~~~~) below the appropriate heading. Use ---- between comments.
General comments (not for a specific tip)
Archive: please don't change text in this box.
These tips have been handled (kept or merged).
Automatically add Python paths to Vim path
Keep
- Good tip. I have tried it, and have edited the tip to add details. --JohnBeckett 04:18, 19 March 2008 (UTC)
- Keep. It's not perfect, (some modules like os.path don't work) but still useful enough to keep. Carpetsmoker 07:45, 14 April 2008 (UTC)
Substitute Word Under Cursor
Merged to VimTip464
- Merge this tip into one of the following (probably 464 where the author added a "see also" to the new tip, with an acknowledgement in the edit summary that it might have been better to put the info in 464).
- Should put a "see also" in 464 with the above list. --JohnBeckett 04:18, 19 March 2008 (UTC)
- Merge 464 Search and replace the word under the cursor is basically the same. -- Carpetsmoker 09:15, 14 April 2008 (UTC)
- I have merged this to 464 and cleaned up 464. --JohnBeckett 06:11, 4 May 2008 (UTC)
- Merge 464 Search and replace the word under the cursor is basically the same. -- Carpetsmoker 09:15, 14 April 2008 (UTC)
VirtualStore
Merged to VimTip1542
- The two mysterious tips we have on Vista are a worry. I hate the idea of deleting an entire directory tree (rmdir /q /s) with no explanation. I'm pretty sure it would be better to work out exactly what the problem is and avoid it. However, perhaps we should keep this tip, with the plaintive comment I've put in it, in the hope that people who understand Vista will one day fix these tips. --JohnBeckett 04:18, 19 March 2008 (UTC)
- I now think the content of this tip should be moved to 1542 Vim on Vista. The author of VirtualStore made only the one contribution, and there has been no feedback to the comments that I added on the tip page. Merging the two rather dodgy Vista tips for later consideration seems safest. --JohnBeckett 06:11, 4 May 2008 (UTC)
- I have merged this to 1542. --JohnBeckett 04:49, 7 May 2008 (UTC)
- I now think the content of this tip should be moved to 1542 Vim on Vista. The author of VirtualStore made only the one contribution, and there has been no feedback to the comments that I added on the tip page. Merging the two rather dodgy Vista tips for later consideration seems safest. --JohnBeckett 06:11, 4 May 2008 (UTC)
Date Time Insert
Merged to VimTip97
- It is already present as VimTip97 --Luc Hermitte 02:32, 19 April 2008 (UTC)
- I agree and added it as a candidate for deletion [changed to merge] and changed the 1 link that was to it other than here. --Ian Kelling August 2008
Match It Plugin
Merged to VimTip6
- Duplicates Moving to matching braces -- User:Carpetsmoker 12:26, 16 April 2008 (UTC)
Switch Lines
Merged to VimTip47
- Merged to Swapping characters, words and lines and kept as a redirect to that tip.
Where to download Vim
Keep
- Original title was "Which verson of Vim should I use?" (with typo). Keep tip and make redirects with various different names to help users find our "how to download Vim" tip. --JohnBeckett 10:10, 20 October 2008 (UTC)
Vis Vim
Merged to VimTip683.
Vis Vim Disinterest
Merged to VimTip683.
- Why two /Vis Vim */ tips?
- Moreover, for those who haven't known the no-longer-supported VC6, this title won't tell what the tip is about.
- I'd rather have only one "Integration with VC/VS" tip. This tip can then have a section related to visvim, or any new system that will take its place. --Luc Hermitte 02:44, 19 April 2008 (UTC)
- I'd be surprised if anyone is even interested in knowing about "Vis Vim", but collecting all "VS integration" tips in one page is a good idea. (Spiiph 18:10, 26 December 2008 (UTC))
Best plugins
Proposal: Replace each of these with a redirect to the new "Best plugins" section on the "Vim scripts" page.
I have put the content (improved) of each of following on the Vim scripts page. I propose keeping each of these names as a redirect to that page (in case the #vim community refer to these links). --JohnBeckett 08:03, 13 January 2009 (UTC)
- Best Plugins as a test, this has already been replaced with a redirect (use its history to see the original)
- Enhanced Commentify Plugin
- Large File Plugin
- NERD Tree Plugin
- Super Tab Plugin
- Surround Plugin
- Surrounding Parens
- Tag List Plugin
Best Tips
This is tutorial material. It contains little of value. (Spiiph 17:46, 26 December 2008 (UTC))
Change GUI Font
File Format
Fix Backspace
Fix Syntax Highlighting
Make a Macro
You can get more information from :h 10.1. There must be better macro tip pages. (Spiiph 17:52, 26 December 2008 (UTC))
New When Hardlinked
New to Vim
Omni Completion
Paste Indent Problems
Read Write System Enviroment Variables
Reselect Visual Block
Super Retab
To Html
I suspect there is already a tip that is about "converting the current document into HTML with respect of current highlighting".
Otherwise, the title is the name of a command that :h will explain. It should instead describes what it accomplishes. --Luc Hermitte 03:00, 19 April 2008 (UTC)
Tutorial Commands
Vim Diff
Define "don't work well". Why is the new version proposed superior? Does vim7(.1?) deprecates this tip? --Luc Hermitte 02:55, 19 April 2008 (UTC)
Vim Gpg
It seems to me that the first and last lines of these four are redundant:
autocmd BufReadPre,FileReadPre *.gpg let ch_save = &ch|set ch=2 autocmd BufReadPre,FileReadPre *.gpg let shsave=&sh autocmd BufReadPre,FileReadPre *.gpg let &sh='sh' autocmd BufReadPre,FileReadPre *.gpg let ch_save = &ch|set ch=2
I'm assuming that saving the default shell value into a temp register, then changing it to the plain unix SHell, isn't going to somehow mess up your ch_save register such that you'd need to re-save the values you just saved before, right? I'm new to Vim scripting, but seriously, this is just a cut-and-paste mistake on somebody's part...?
- Forgot to use ~~~~? In any case, the current tip contains a lot of crap. I've added a comment with an improved, but untested version. It could probably be improved further. (Spiiph 18:02, 26 December 2008 (UTC))
Vim IRC FAQ
Random collection of :help commands. It could perhaps be merged with a FAQ, if there is one. (Spiiph 18:04, 26 December 2008 (UTC))
Vim Tutor
This is just :h vimtutor. (Spiiph 18:06, 26 December 2008 (UTC))