diff options
author | Jay Berkenbilt <ejb@ql.org> | 2022-02-08 15:18:08 +0100 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2022-02-08 17:51:15 +0100 |
commit | cb769c62e55599e9f980001830bc61d9fcaa64a9 (patch) | |
tree | 0bf980c385a61cbc8720cf990762ffc1200f9d6a /examples/qtest/qpdfjob-c.test | |
parent | 716381f65a2b2dc72f8da2426ba71aeab02c507f (diff) | |
download | qpdf-cb769c62e55599e9f980001830bc61d9fcaa64a9.tar.zst |
WHITESPACE ONLY -- expand tabs in source code
This comment expands all tabs using an 8-character tab-width. You
should ignore this commit when using git blame or use git blame -w.
In the early days, I used to use tabs where possible for indentation,
since emacs did this automatically. In recent years, I have switched
to only using spaces, which means qpdf source code has been a mixture
of spaces and tabs. I have avoided cleaning this up because of not
wanting gratuitous whitespaces change to cloud the output of git
blame, but I changed my mind after discussing with users who view qpdf
source code in editors/IDEs that have other tab widths by default and
in light of the fact that I am planning to start applying automatic
code formatting soon.
Diffstat (limited to 'examples/qtest/qpdfjob-c.test')
-rw-r--r-- | examples/qtest/qpdfjob-c.test | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/examples/qtest/qpdfjob-c.test b/examples/qtest/qpdfjob-c.test index 33a55431..a01b2c64 100644 --- a/examples/qtest/qpdfjob-c.test +++ b/examples/qtest/qpdfjob-c.test @@ -12,12 +12,12 @@ cleanup(); my $td = new TestDriver('qpdfjob-c'); $td->runtest("qpdfjob-c", - {$td->COMMAND => "qpdfjob-c in.pdf a.pdf"}, - {$td->STRING => "", $td->EXIT_STATUS => 0}, + {$td->COMMAND => "qpdfjob-c in.pdf a.pdf"}, + {$td->STRING => "", $td->EXIT_STATUS => 0}, $td->NORMALIZE_NEWLINES); $td->runtest("check output", - {$td->FILE => "a.pdf"}, - {$td->FILE => "out.pdf"}); + {$td->FILE => "a.pdf"}, + {$td->FILE => "out.pdf"}); cleanup(); |