Shohoo

> The break up happens too soon as the semicolon is not above col pos 80 as specified (it is at col 78) Well so it seems to be deeper...

I think you did not understand. In my opinion result: ``` ffffffff( "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n", aaaaaaaaaaaa, bbbbb->bbbb.bbbbb.bbbb.bbb, ccccc->cccc.ccccc.cccc); ffffffff( "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n", aaaaaaaa, bbbbbbbb, cccccccc, ddddddddd); ``` should occur even if ls_code_width = false....

I have added third case to previous two: ``` //1 case ffffffff("xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n", aaaaaaaaaaaa, bbbbb->bbbb.bbbbb.bbbb.bbb,ccccc->cccc.ccccc.cccc); //2 case ffffffff("xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n", aaaaaaaa, bbbbbbbb, cccccccc, ddddddddd); //3 case ffffffff("xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n", aaaaaaaa, bbbbbbbb, cccccccc, ddddddddd); ``` results...

Ok, so it is a bug. I would live with that but there is my original problem with newline after ternary condition. Tell me, can you do sth with that...

Any progress?