Perhaps as a staffer you are immune to the automated welcome? At any rate, welcome to the Vim wiki, and we will know who to contact with any problems! Perhaps you know that Tim Starling is also a Vim user, so you are not alone. Shout (here will do) if you have any Vim problems. This wiki is very quiet, but I hope to return in due course and do some more serious work in cleaning it up. Most of the tips need a lot of fixing, but there are lots of gems, and even basic stuff like searching (and the pages it links to) is worth browsing.
BTW, do you have privileges here? If so, have a look at Special:AbuseFilter for a laugh. There are currently 379 hits since 10 December (and I think only 2 were false positives). JohnBeckett (talk) 11:00, February 8, 2013 (UTC)
Thanks for the welcome! (I'm not surprised we're not employing CPU cycles to welcome ourselves ;])
This wiki is pretty awesome indeed and I'll definitely stick around.
May I ask what's the relationship between this project and the main site (vim.org)?
I'd love to help somehow, I've got full rights (WikiaStaff and Wikia utils), that includes enabling/disabling any kind of extensions (also those not available to admins) and as part of Wikia's Engineering I know the platform pretty well.
BTW, you cannot imagine the crazy stuff we get to see in the logs of the "spam wikis" (i.e. wikis created for the sole scope of spamming our network) cron job... XD
Lox federico (talk) 20:59, February 8, 2013 (UTC)
There's some "origin" information at Vim Tips Wiki:About, but I'll add a long note with some details as it may be of interest to you or others in the future. Originally, vim.org (a Sourceforge site) hosted both tips and scripts. Anyone could quickly register and add a tip, and each tip page had an "add comment" feature where anyone could add whatever they liked (it went at the bottom). Only the script author could modify a script page (but it is easy for anyone to become an author and create/maintain their script pages). Vim was and is written by Bram Moolenaar, and Bram likes things to be as open as possible, and the old system worked well for some years. There was a major problem, namely that the tip pages were not editable, and not even the tip author could alter the content. All that was possible was to add a comment at the bottom. The result was that a tip would be created, then some content-free comments would be added, then someone would point out a much better approach, or a bug, or some improvement. There was no way to clean the mess up, and stuff just kept accummulating.
Then the reality of the Internet hit, and around 2007 the spammers got busy. There had been spam problems before, but they were manually cleaned up with difficult manual editing of the PHP source (by changing fields in the MySQL database!). From 2007, it was obvious to everyone that the spammers could not be handled anymore, so Bram disabled the "add comment" feature, and the tips were frozen for some months. However, spammers added new tips with 100% spam, and we were desperate. The vim_use mailing list (for info, click "Community portal" in the sidebar) discussed what to do for months. I gave lots of advice during that time, but did nothing. In those days (early 2007), Wikia was picky, and you had to apply to create a wiki. The founder of this wiki (Tom Purl) was the person from the mailing list discussion who arranged with Wikia (mainly Angela, I think) to create the wiki. Tom didn't have time to do much more than set up a couple of things, but he played that vital role. Then there was several more weeks of discussion of how to copy the tips from vim.org to the wiki, and whether all the junk comments should be copied. Finally, Bastl got tired of waiting for a conclusion to the discussion, and he spent a few days writing Python scripts to scrape vim.org/tips and create wiki pages. Then a few of us got busy trying to clean everything up. It was a complete shambles with many problems. The original imported tips enclosed the tip in a template, with all comments underneath. However, many of the tips use funny punctuation which completely broke the template. Also, Bastl's scripts changed every "@" to "--AT--" because there were a lot of email addresses in the comments. Of course, that broke many tips which used the "@" character. There was more similar stuff. Several people got stuck in and cleaned tips, but it was too hard to do it one at a time, so I wrote some Python to download tips to a local computer, where I was able to edit the wikitext in Vim, doing bulk changes. Another script uploaded them (after checking that no edits had occurred while I had been working). After a year or two, and the work of lots of people, the tips reached a "clean" state where nearly all junk comments (and all spam) had been removed, and template/punctuation problems fixed. Then a few of us stayed on to try to fix the tip content by removing obsolete or misguided material, and merging helpful suggestions. Just fixing blatantly bad tip titles (info) took ages, and that's after fixing titles which originally had invalid punctuation.
Bram is very happy that someone else (us) gets to worry about the tips now, and he has no real interest in what happens here because he has to devote his time to maintaining Vim. The original vim.org/tips pages were lost when the Sourceforge system crashed and no good backup was available (each of the old tips was read-only, and had a link to the corresponding page here). There is now just one page which links here (http://www.vim.org/tips/).
The vim.org/scripts pages still operate (and I occasionally have to remove spam from there by executing SQL delete statements). Each vim.org/scripts page links to a page for comments on this wiki (Bram did that). For example, see the "Vim wiki" link at the top of script 2981 which links to Script:2981.
Thanks for the in-depth look into the wiki's origins.
So my understanding is that the current "mission" is to cleanup and review the tips with the main goal to remove those that aren't working anymore?
Is there any other initiative going on on the wiki (random examples from the top of my head: reworking the navigation, switching to using Wikia's comments/forums instead of the manual "comments" section in each page, use GeSHI for adding syntax highlighting to vimscript snippets, prepare different portals for different users levels like beginner, intermediate, advanced linked to relevant stuff)?
I'd be happy to contribute somehow.
Lox federico (talk) 17:19, February 9, 2013 (UTC)
That's right, we want to clean up or merge as many tips as possible. We'll probably never get that finished, but my hope is that we would fix the core content (what a Vim user should know), and leave esoteric stuff for the far future.
There are some useful ideas at Vim Tips Wiki:Todo, which I put roughly in order with the most achievable or desirable first. The new tips issue mentioned there is a pressing problem. I occasionally get a burst of energy and time and fix a couple of months, but I got stalled with some important tips which are a shambles and which need a lot of cleaning up. We like to only accept a new tip if it really is new. Often new tips should be merged into existing tips (we generally merge so that the final tip ends up on the lowest tip number, that is, the first on the topic), and that is what stalled me. I have a lot of nearly finished work on my computer where I've looked at a dozen tips on a particular topic and have nearly worked out what I want to do to merge them. I hate promoting a new tip to a "permanent" tip when I know that the material should be treated on another page. Apart from the tidiness of merging, the real problem with keeping every tip is that the duplication makes finding useful information very difficult.
There is a tension between merging all related information into one gigantic tip (everything in one place), and the benefit of having short and digestible tips (short tips are more readable and useful).
If you feel inclined, any progress with new tips would be good, but you probably should ignore difficult cases, and look for reasonably simple stuff to start. We avoid deleting new and old tips unless they are quite unhelpful, preferring to make them a redirect to some earlier tip roughly on the same topic. That helps preserve incoming links to avoid irritating readers, and is kinder to the author.
We have used GeSHi (see CSV for example), but we're not really sure how useful it is. We use lots of
<pre>...</pre> (putting the tags on their own lines to make working on the wikitext easier), and that is more legible and seems good for a few lines.
Portals might be useful in the future, but the essential problem now is that we lack useful advice in a lot of areas (see vimrc which is linked from a hundred tips). It would be good to have a series of tips for beginners to show them what to do, and to that end we have Category:Getting started. Cleaning up or expanding tips in that category would be good. When in a reasonable state, we could work out how to promote the category and make it easier to find/use (perhaps a list that might go on one of: New to Vim or Vim IRC FAQ or Quick tips).
Navigation is tricky. Do you mean something like categories in concept but which is easier for non-wiki readers, or do you mean the two lines at the top of each tip which give the tip number and the fairly useless previous/next links, with some often obsolete info about the author/status? Any ideas would be good, but you might not get much enthusiasm from me until we are able to link to useful advice. JohnBeckett (talk) 07:24, February 10, 2013 (UTC)
Hey, sorry for the late reply :)
Re: Navigation, what I meant is both categorization and refreshing the navigation bar at the top of the page (the one which currently hold "on this wiki", "community portal" and "todo", with the last two being empty sub-menues).
Concerning the "starter guide", I'd be happy to work on that if you guys don't mind as I'm learning now and know pretty well what a beginner would be searching for.
Let me know. Lox federico (talk) 14:58, February 14, 2013 (UTC)