diff options
author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2019-04-30 18:51:47 +0100 |
---|---|---|
committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2019-04-30 18:56:21 +0100 |
commit | b0993336112b244ea7e919d96ffdbaf167831b9d (patch) | |
tree | 57e00b4bea4f11254e1de31454176bdc4e80c208 /reproduce/analysis/bash/download-multi-try | |
parent | cd73f88157764334e96fa6f286687e3fa9b061fd (diff) |
End-of-line Backslashs no longer right under each other
When we need to quote the new-line character we end the line with a
backslash (`\'). Until now, our convention has been to put all such
backslashes under each other to help in visual inspection.
But this causes a lot of confusion in version control: if only one line's
length is larger, the whole block will be marked as changed and thus makes
it hard to visually see the actual change. It also makes debuging the code
(adding some temporary lines) hard.
With this commit, I went through all the files and tried to fix all such
cases so only a single white space character is between the last command
character and the backslash. Where there was an empty line (ending with a
backslash, to help in visually separating the code into blocks), I put the
backslash right under the previous line's.
This completes task #15259.
Diffstat (limited to 'reproduce/analysis/bash/download-multi-try')
0 files changed, 0 insertions, 0 deletions