Mercurial > ~mikael > mcabber > hg
view mcabber/CodingStyle.txt @ 2190:ee3a40ffcd8b
New option: 'clear_unread_on_carbon'
If the new 'clear_unread_on_carbon' option is set to 1, clear the unread
message flag for a contact whenever an outgoing carbon copy of a message
sent to that contact is received from another client.
---
mcabber/mcabber/commands.c | 2 +-
mcabber/mcabber/hbuf.h | 1 +
mcabber/mcabber/hooks.c | 17 ++++++++++++-----
mcabber/mcabber/hooks.h | 2 +-
mcabber/mcabber/screen.c | 18 ++++++++++++++----
mcabber/mcabber/xmpp.c | 2 +-
mcabber/mcabberrc.example | 5 +++++
7 files changed, 35 insertions(+), 12 deletions(-)
author | Holger Weiß <holger@zedat.fu-berlin.de> |
---|---|
date | Thu, 23 Jul 2015 23:44:45 +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