Hello, Sebastian Menge <[EMAIL PROTECTED]>:
> How should we deal with that? > > One way would be a family "C" with subcats c-plain, c++, c# etc. (java?) That's what I tried to do with C++. BTW, at first, I could edit [[:Category:C++]], now I can't even read it. I don't know why. NB: I know a category named "C++" could be access in mediawikis. See for instance wikipedia where it work perfectly. The URL is of course encoded, but the text on the pages is readable as "C++". > But since vim is used heavily for c and c++ programming, i guess there > are many tips in that categories, so i would propose to use only one > level with c, c++, c# below LanguageSpecific. That's sound perfectly valid to me. The only problem I see is that I don't really like duplicating all the C tips in C++ category. > In general I could imagine to have _only_ one sublevel under > LanguageSpecific. The list could get long, but anyways. > > Now on naming: > > C and C++ seem ok ? > > C sharp is the only thing i can think of. "Gtk Sharp" is mentioned on the > wikipedia article on "naming". I'm not sure to understand what you are referring to. > How about C/C Plus Plus in tip titles? I would remove it because it's in > the categories. Yes and no. The problem with removing it is when a tip is in several orthogonal categories. Like for instance Automated_Text_Insertion, or Compiler, ... plus the language category. May be. We could add a "_(/language/)" (e.g. "_(C++)", "_(Perl)", ...) at the end of the tip title. > As I write this, things seem so clear to me that i'll be bold ;-) If > youre unhappy with something, just say so, everything can be reverted. -- Luc Hermitte _______________________________________________ Vim-l mailing list [email protected] http://lists.wikia.com/mailman/listinfo/vim-l
