[Vim-l] Titles project

John Beckett johnb.beckett at gmail.com
Thu Oct 4 12:08:53 UTC 2007


hermitte wrote:
>> 221 Indenting "throws" in java
>> 221 Indenting java throw statements
>> OK 221 Indent Java throw statements
> 
> "Indent" or "Indenting" ?

Hmmm. Good question. Which of the following??
221 Indent Java throw statements
221 Indenting Java throw statements

The first seems to be a command saying that any Java throw statements
*should* be indented.

The second seems to be about *how* you indent Java throw statements (more
appropriate for a tip).

>> --> 376 Build vim with your name included
>> # Sebastian has suggested deleting this tip.
>> # I will add {{delete}} if you don't object.
> 
> I like the other proposition that have been made in other 
> emails about customizing Vim.

But tip 376 contains only one useful line that points out that if you knew
how to build Vim, you could put any name you wanted into the "compiled by"
option (whereas by default, you get your logged-on username at hostname).

That's a very weak start to a tip about how to build Vim!

I'm looking for:
- Agreement to delete tip 376, or
- A title for 376 that won't cause despair to a reader.

>> 683 HOWTO - Integrate MS .NET and gvim.exe
>> 683 Integrate Visual Studio and gvim
>> OK 683 Integrate gvim with Visual Studio
> 
> The ".NET" information is a very important one that must not 
> be discarded.
> Vim 5.x could be integrated with VS6. However, as VS.NET API 
> changed, we could not integrate Vim with it anymore. Hence this tip.

But the only Visual Studio you can get for the last several years is .NET.
If we have a tip about integrating Vim with VS 6.0, we perhaps should spell
out that the tip is *not* about VS .NET.

All tips now should assume that "Visual Studio" means a reasonably current
VS, which means .NET.

So, whereas I'm sure that your understanding of the background is valid, is
there a practical reason for needing ".NET" in the title in 2007?

>> OK 945 Run Vim command on current C/Cpp/Java function
> 
> It's not just C, C++, and Java. It's also (B,?) D, C#, PHP, 
> etc. In other words, this tip concerns all C-like languages.
> Moreover, as stated in the comments, it does not integrate 
> that well with C++, and definitivelly not well at all with Java.

Are you suggesting it should be one of:
945 Run Vim command on current function in C programs
945 Run Vim command on current function in C-like programs

John



More information about the Vim-l mailing list