mcabber/CodingStyle.txt
author Holger Weiß <holger@zedat.fu-berlin.de>
Sun, 26 Jul 2015 22:45:56 +0200
changeset 2308 e8c8665c824e
parent 1509 189ffdd944b4
child 2337 ffd0e57e9563
permissions -rw-r--r--
Let <Enter> (un)fold groups in vi mode When the input line is empty and the user hits the <Enter> key on a roster group name, (un)fold that group even if vi_mode is set to 1. --- mcabber/mcabber/screen.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)

This document describes the preferred coding style for the mcabber project.

If you intend to patch and contribute to mcabber, please try to use the
existing style, and read the following points.

- Do not use tabs, use space characters;
- Avoid trailing whitespace;
- Avoid lines longer than 80 characters;
- Indentation is 2 spaces (ok, maybe it isn't a good idea but it's the
  current style);
- Put a space after non-functions statements (e.g. if, while...)
- Put the opening brace last on the same line, and put the closing brace first
  except for functions, where the opening brace should be alone on a new line.

  Example:

    void example(void)
    {
      if (cond1) {
        do_a();
      } else if (cond2) {
        do_b();
      } else {
        do_c();
      }

      if (error)
        exit(0);
    }

 - Look at existing code for rules not mentioned here.

Mikael