Vim Tips Wiki
(opinions on remaining tips)
(one more done)
Line 34: Line 34:
 
| [[Delete C Function]]
 
| [[Delete C Function]]
 
|align="center"| [[#Delete C Function|''discuss'']]
 
|align="center"| [[#Delete C Function|''discuss'']]
|align="center"| -
+
|align="center"| Merged to [[VimTip1130]]
 
|-
 
|-
 
| [[Quickfix and doxygen]]
 
| [[Quickfix and doxygen]]
Line 79: Line 79:
   
 
==[[Delete C Function]]==
 
==[[Delete C Function]]==
  +
'''Merged''' to [[VimTip1130]] (which I will generalise). [[User:JohnBeckett|JohnBeckett]] 10:37, 23 June 2009 (UTC)
  +
----
 
'''Merge''' to somewhere in a tip on editing source code. I'll think about where later. [[User:JohnBeckett|JohnBeckett]] 11:29, 30 May 2009 (UTC)
 
'''Merge''' to somewhere in a tip on editing source code. I'll think about where later. [[User:JohnBeckett|JohnBeckett]] 11:29, 30 May 2009 (UTC)
 
----
 
----

Revision as of 10:37, 23 June 2009

New tips February 2009

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
Associate vimprojects file with vim discuss -
Auto tags by project.vim discuss Keep
Default filetype discuss -
Delete C Function discuss Merged to VimTip1130
Quickfix and doxygen discuss Keep
Remap CapsLock or other keys without reboot in Windows discuss Merged to VimTip75
Sticky shift-enter (way to avoid Esc) discuss Merged to VimTip285
User input from a script discuss Keep
Using Git from Vim discuss Keep
View text file in two columns discuss Keep

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

General comments (not for a specific tip)

Associate vimprojects file with vim

Merge? I don't like the registry tips (for one thing, they inevitably will cause trouble on some systems). I don't see the point of this being a separate tip (it's really something to do with Windows), and I'll think about merging the "Using console utilities" section into the next tip, which is also on project.vim. JohnBeckett 11:29, 30 May 2009 (UTC)


I think this is a pretty good stand-alone tip, mainly because I wouldn't have thought of doing it, even though it is fairly obvious and potentially very useful. If we had a generic "using project.vim" tip maybe we could merge, but I don't think we do. That being said, I mostly agree; registry tips always make me nervous. How about we create an "editing the registry is dangerous" template that we can add to all the registry tips (including the one I'm working on) with text similar to that which I just added to this tip?

Auto tags by project.vim

Keep I haven't studied this, but it seems good. JohnBeckett 11:29, 30 May 2009 (UTC)

Default filetype

Merge to 1606 Filetype.vim. There must be a better way to do this? Can someone check it. I think the result should go in 1606. JohnBeckett 11:29, 30 May 2009 (UTC)


Agreed. Though Filetype.vim says it is about the filetype.vim file itself...don't we have a generic "using filetypes in Vim" tip? --Fritzophrenic 14:49, 22 June 2009 (UTC)

Delete C Function

Merged to VimTip1130 (which I will generalise). JohnBeckett 10:37, 23 June 2009 (UTC)


Merge to somewhere in a tip on editing source code. I'll think about where later. JohnBeckett 11:29, 30 May 2009 (UTC)


Agreed, I don't find this tip very useful by itself. I can't think of anywhere to merge it to though. Do we need a new "merge this tip somewhere" category/template? --Fritzophrenic 14:49, 22 June 2009 (UTC)

Quickfix and doxygen

Keep JohnBeckett 05:22, 21 June 2009 (UTC)


Try to merge to a compiler tip? The only tip dealing with doxygen is 653 Continuing doxygen comments. If can't think of anything better, perhaps merge this new tip to 653 and rename it to something more general like "Working with doxygen files"? JohnBeckett 11:29, 30 May 2009 (UTC)


My vote is actually to keep both of these tips, separately. Doxygen is not a filetype by itself, it's an external program that processes specially formatted C comments, similar to javadoc but with much more information included in the report. I've used it a couple times, it's really nice. I think that it only works with C code, so we can probably put it in Category:C, possibly in a new subcategory. --Fritzophrenic 02:18, 31 May 2009 (UTC)

Remap CapsLock or other keys without reboot in Windows

Merged to 75 Map caps lock to escape in Windows. JohnBeckett 11:29, 30 May 2009 (UTC)

Sticky shift-enter (way to avoid Esc)

Merged to 285 Avoid the escape key. I have done a lot of work lately to merge all the exotic "avoid escape" tips, and I don't want a new separate tip however interesting. This new material (by Benatkin from Ben Atkin's blog) is a great idea, although the author later blogged that he stopped using the mapping because it was hard to accept the inconsistency of how Shift-Enter worked. I have reworked it and merged into 285. JohnBeckett 07:49, 2 June 2009 (UTC)

User input from a script

Keep I have rewritten the tip with an example, and made it more general. Some tips use input(), but none explain it. JohnBeckett 11:29, 30 May 2009 (UTC)

Using Git from Vim

Keep We have nothing on git or VCSCommand; perhaps expand later. JohnBeckett 11:29, 30 May 2009 (UTC)

View text file in two columns

Keep I have fixed this by merging solutions and cleaning. JohnBeckett 11:29, 30 May 2009 (UTC)