Vim Tips Wiki
Line 298: Line 298:
   
 
==[[Vim IRC FAQ]]==
 
==[[Vim IRC FAQ]]==
  +
Random collection of <code>:help</code> commands. It could perhaps be merged with a FAQ, if there is one. ([[User:Spiiph|Spiiph]] 18:04, 26 December 2008 (UTC))
   
 
==[[Vim Tutor]]==
 
==[[Vim Tutor]]==

Revision as of 18:04, 26 December 2008

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.

Tips from Vim Tips wiki
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


Suggestion: Leave consideration of the following until Metacosm returns.
--JohnBeckett 06:11, 4 May 2008 (UTC)

Tips from Metacosm
Proposed new tip Link Current consensus
Best Plugins discuss -
Best Tips discuss -
Change GUI Font discuss -
Date Time Insert discuss Merged to VimTip97
Enhanced Commentify Plugin discuss -
File Format discuss -
Fix Backspace discuss -
Fix Syntax Highlighting discuss -
Large File Plugin discuss -
Make a Macro discuss -
Match It Plugin discuss -
NERD Tree Plugin discuss -
New When Hardlinked discuss -
New to Vim discuss -
Omni Completion discuss -
Paste Indent Problems discuss -
Read Write System Enviroment Variables discuss -
Reselect Visual Block discuss -
Super Retab discuss -
Super Tab Plugin discuss -
Surround Plugin discuss -
Surrounding Parens discuss -
Switch Lines discuss Merged to VimTip47 (title kept as redirect)
Tag List Plugin discuss -
To Html discuss -
Tutorial Commands discuss -
Vim Diff discuss -
Vim Gpg discuss -
Vim IRC FAQ discuss -
Vim Tutor discuss -
Vim on Freenode discuss -
Vis Vim discuss -
Vis Vim Disinterest discuss -
Where Are My Settings discuss -
Where to download Vim discuss Keep

Please add your comment (sign with --~~~~) below the appropriate heading. Use ---- between comments.

General comments (not for a specific tip)

Automatically add Python paths to Vim path

We have finished discussing this tip – it has been kept.


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

We have finished discussing this tip – it has been merged, and will be deleted.


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)

VirtualStore

We have finished discussing this tip – it has been merged, and will be deleted.


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)

Best Plugins

Best Tips

This is tutorial material. It contains little of value. (Spiiph 17:46, 26 December 2008 (UTC))

Change GUI Font

Date Time Insert

We have finished discussing this tip – it has been merged.

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

Enhanced Commentify Plugin

File Format

Fix Backspace

Fix Syntax Highlighting

Large File Plugin

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

Match It Plugin

Duplicate Moving to matching braces -- User:Carpetsmoker 12:26, 16 April 2008 (UTC)


NERD Tree Plugin

New When Hardlinked

New to Vim

Omni Completion

Paste Indent Problems

Read Write System Enviroment Variables

Reselect Visual Block

Super Retab

Super Tab Plugin

Surround Plugin

Surrounding Parens

Why two tips? BTW, there are other surrounding plugins. --Luc Hermitte 02:52, 19 April 2008 (UTC)

Switch Lines

We have finished discussing this tip – it has been merged. Merged to Swapping characters, words and lines and kept as a redirect to that tip.

Tag List Plugin

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

Vim on Freenode

Vis Vim

Vis Vim Disinterest

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)

Where Are My Settings

Where to download Vim

We have finished discussing this tip – it has been kept.


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)