summaryrefslogtreecommitdiff
path: root/htdocs/huh.php
blob: eda3fd0575fb1c36e765e82545f66e4f28c69957 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
<?php
// explanation about vim online tips and scripts
require_once("include/init.inc");
$page_title = "huh?";

include("header.php");
?>
<h1>About Vimonline</h1>
<p>
This is a place where users of the vim editor can add their 
favorite scripts, commands, macros and other assorted tips to a common database. 
Both scripts and tips have <a href="karma.php">karma</a> allowing the community
to rate their usefulness.
</p>
<p>
<b>If you have questions about the vim editor, please use the <a href="community.php">vim mailing list</a>. Not vimonline support.</b>
</p>
<p>
If you have feedback on the site feel free to contact 
<b>vimonline-support at lists.sourceforge.net</b>
directly at <b>scrott at users.sourceforge.net</b> and <b>jmorace at users.sourceforge.net</b>.
Be sure to check the current <a href="https://sourceforge.net/tracker/?atid=391890&group_id=27891&func=browse">feature requests</a> before suggesting a feature. You can also check out the current 
vim online <a href="https://sourceforge.net/tracker/?atid=391887&group_id=27891&func=browse">bugs</a> as well. I try and keep all the feature requests and bugs in the sourceforge trackers. 
For more details you can check out the <a href="http://vimonline.sf.net">vimonline development site</a>.
</p>
<h2>Scripts</h2>
<p>As more people develop scripts for vim it is important to have a central place
to store them. vim online provides a place to upload a script (general utility,
syntax, indent, etc...) and then continue to provide updated versions of that
same script.
<h2>Tips</h2>
<p>
While the vim distribution comes with a rich set of documentation it is often hard
to find a place to start when trying to incrementally learn how to use the
editor. When I realized how much I was learning from the vim list alone I
thought it would be great to have a place that the community could maintain
a list of their favorite vim gems. The overall goal is to have a place you 
can visit when you are in a vim learning mood or when you "discover" something 
particularly powerful and want to share it with other vim users. 
<span class="errortext">Please remember vim tips are not meant to be
documentation!</span> Tips should have pointers to where you can read more
about the feature in help or on the web.
</p>
<p>
Editing tips on the vim.org website was disabled because of an overload of 
spam.
As a solution, and offering much more functionality, all the tips were 
copied to the Tips wiki.
<p>
This is the new place to edit and add tips:
<b><a href="http://vim.wikia.com/wiki/Main_Page">Vim Tips wiki</a></b>
<p>
On this site you can still find the read-only list of the tips from before the
wiki was created.
</p>
<p>
Each tip has a complexity:
<img src="tips/images/basic.gif" alt="basic"> basic, 
<img src="tips/images/intermediate.gif" alt="intermediate"> intermediate and
<img src="tips/images/advanced.gif" alt="advanced"> advanced (taken from the standard ski hill
levels). Please consider these levels when creating tips. 
</p>
<p>
<h2>Authentication</h2>
<p>
Authentication was not required to create a tip. We felt it was important
there was no barrier to entry for tip creation.  But spammers abused it :-(.
</p> 

<p>In order to upload scripts you must have an account with vim online. This is
so there can be defined contact people for scripts to avoid confusion.
User passwords are stored using one-way encryption.
</p>
<p>
<h2>Why ads?</h2>
<p>
For a long time there were a few links near the bottom of the page.  This
helped Bram pay his mortgage.  But the company taking care of this stopped.
<p>
Now we have Google Ads.  We hope they are not too distractive.  They do help
pay the bills.
</p>
<?php
$google_ads = "big";
include("footer.php");
?>