diff options
author | Simon Tatham <anakin@pobox.com> | 2022-08-03 22:48:46 +0300 |
---|---|---|
committer | Simon Tatham <anakin@pobox.com> | 2022-08-03 22:48:46 +0300 |
commit | 4fa3480444a64a5be3055cf27d96d8e68d0a1d12 (patch) | |
tree | 96cb29b2d2a28a453d3789125d41c3c542bd4df5 /terminal | |
parent | 3a42a09dadcb38e4f3481a4dd8b4c2bad5b6de4b (diff) |
Formatting: realign run-on parenthesised stuff.
My bulk indentation check also turned up a lot of cases where a run-on
function call or if statement didn't have its later lines aligned
correctly relative to the open paren.
I think this is quite easy to do by getting things out of
sync (editing the first line of the function call and forgetting to
update the rest, perhaps even because you never _saw_ the rest during
a search-replace). But a few didn't quite fit into that pattern, in
particular an outright misleading case in unix/askpass.c where the
second line of a call was aligned neatly below the _wrong_ one of the
open parens on the opening line.
Restored as many alignments as I could easily find.
Diffstat (limited to 'terminal')
-rw-r--r-- | terminal/terminal.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/terminal/terminal.c b/terminal/terminal.c index b6d97c4b..5310c650 100644 --- a/terminal/terminal.c +++ b/terminal/terminal.c @@ -647,7 +647,7 @@ static void makeliteral_truecolour(strbuf *b, termchar *c, unsigned long *state) * Put the used parts of the colour info into the buffer. */ put_byte(b, ((c->truecolour.fg.enabled ? 1 : 0) | - (c->truecolour.bg.enabled ? 2 : 0))); + (c->truecolour.bg.enabled ? 2 : 0))); if (c->truecolour.fg.enabled) { put_byte(b, c->truecolour.fg.r); put_byte(b, c->truecolour.fg.g); |