Wikia

Vim Tips Wiki

Talk:Tip

1,610pages on
this wiki

Back to template

Shouldn't we use the real title and not the obfuscated title in the tips ?

For instance, it is hard to understand what the title of "%"_doesn't_work_in_C_HASH_for_HASH_region_and_HASH_endregion really means.

"%" doesn't work in C# for #region and #endregion

will be more appropriate I think.

NB: I'm not speaking about renaming the pagename, but using the title parameter of the {{Tip}} template.

--Luc Hermitte 14:32, 12 June 2007 (UTC)

Hmm, i would like to have both the pagename and the title consistent because they are the same (in terms of MVC, if you understand ...). Therefore i used {{PAGENAME}} in the template. I would propose to find better pagenames, that kills two birds with one stone .. bastl 15:51, 12 June 2007 (UTC)
In that case, with the constraint that the pagename and the title must be equal, the title parameter is just useless. Still, IMHO, we can use it to have human-friendly tip-titles.
I agree that renaming pages (and hence their pagenames) is the main thing to do. However, there are many titles (and even pagenames) that need these URL-unfriendly characters: all those that contains C++, C#, ... I understand there is a limitation in (media?)wiki which implies obfuscated URL and pagenames. But I see no reason to have an obfuscated tip-title as well. At least, as long as we keep one tip here for each one on vim.org. If this "matching" were to be given up, the tip-title won't need to be kept either.
--Luc Hermitte 18:55, 12 June 2007 (UTC)

Optional deprecated field? Edit

On the forum I proposed a deprecated template, but I think it'd make more sense to have an optional deprecated field for this template, basically deprecated = reason. -- Heptite 11:57, 23 June 2007 (UTC)


That's a good idea. However, it might be tricky to get it to work well in practice. I've been reading how templates and optional parameters work, and have almost got it figured out, so I'm speculating that it would be difficult to implement cleanly.

The advantage of your earlier Deprecated template is that it would be easy to implement, including giving a prominent warning box and a Deprecated category.

I will repeat my earlier comments in the hope of getting some feedback:

  1. 1500 tips is just too many! Too many to maintain, but mainly too many to be of use for a reader. (So we need to delete weak tips.)
  2. Many tips (like your example Compiler for perl) are obsolete or very weak. You could spend an hour polishing them, but the result would still be pathetic.
  3. I favour a triage: Do a quick clean of good tips (30%), fully delete obsolete/weak tips (30%), then concentrate efforts on the middle 40% where significant refactoring is required (like merging similar tips).

--JohnBeckett 03:40, 24 June 2007 (UTC)


Since there's no major objections, I've gone ahead and added this, see the above linked forum page for details. -- Heptite 01:14, 4 July 2007 (UTC)

Around Wikia's network

Random Wiki