Commit 878ae331 authored by Christoph Cullmann's avatar Christoph Cullmann

fixup some links

parent bce81674
......@@ -10,7 +10,8 @@ If you want to help us develop Kate, KWrite or KatePart, you should <a title="Ka
### How to Build Kate
Right now, you can build Kate very easily provided you use at least KDE 4.6. <a title="Building Kate" href="/?p=274" target="_self">Click here for a quick howto</a>. We are always happy about patches, just send them to our [mailing list][1]!
Kate can easily be build on a current Linux distribution, we provide a [how-to](/build-it/) for this.
For other operating systems, the [how-to](/build-it/) page provides extra links with information.
### Areas of work
......@@ -27,14 +28,6 @@ The main work area is the programming, but if you are not a programmer you can h
The code in ktexteditor.git and kate.git shall follow the style described for <a href="https://techbase.kde.org/Policies/Kdelibs_Coding_Style" target="_blank">KDELIBS</a>.
### Coding Standards for Python Plugins
Besides delimiting blocks with 4 spaces, we do not have very strict rules for coding new Python plugins, basically having this kate variable line in your source files will do:
<pre># kate: space-indent on; indent-width: 4; mixed-indent off;</pre>
In addition, most of us follow the PEP-8 style guide wherever appropriate. Who codes desides. If you are changing an existing plugin that follows the PEP-8 rules, please follow too.
### Documenting your code
We use Doxygen syntax to document code, and it&#8217;s nice to document everything, even private code, since other people than you might get to work on it or just try to understand it.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment