view mcabber/CodingStyle.txt @ 2193:18fa5ecb1ef4

Make sure outgoing carbons won't set unread flag Outgoing carbon copies received from other clients shouldn't set the unread messages flag if it wasn't set before (regardless of the 'clear_unread_on_carbon' option). --- mcabber/mcabber/hooks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
author Holger Weiß <holger@zedat.fu-berlin.de>
date Tue, 28 Jul 2015 00:27:12 +0200
parents 189ffdd944b4
children ffd0e57e9563
line wrap: on
line source

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