New tips October 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.

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

General comments (not for a specific tip)

C++ code completion

Keep, in Category:Plugin? I think it could be useful to have a collection of "how to configure X plugin" tips, though perhaps an example such as this would be better placed in the help docs for the plugin. --Fritzophrenic 21:47, 1 February 2009 (UTC)

Keep. Will add as a "see also" in 1591 Omni completion, and probably move a few lines from 1591 to the new tip. Probably need "see also" in VimTip1439 also. I think 1591 can be an overview tip; when we get sufficient details for a particular topic to warrant it, they can be moved to a separate tip (like all C++ completion stuff in this new tip). JohnBeckett 10:13, 5 April 2009 (UTC)

Save as sudoer

Merge to Su-write --Fritzophrenic 21:47, 1 February 2009 (UTC)

Agree. JohnBeckett 10:13, 5 April 2009 (UTC)

Subversion developer cindent options

Keep (though looking at the code snippet that uses this cindent setting makes me never, ever want to edit Subversion code). --Fritzophrenic 21:47, 1 February 2009 (UTC)

Agree. JohnBeckett 10:13, 5 April 2009 (UTC)