summaryrefslogtreecommitdiffstats
path: root/examples/qtest/count-strings.test
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2022-02-08 15:18:08 +0100
committerJay Berkenbilt <ejb@ql.org>2022-02-08 17:51:15 +0100
commitcb769c62e55599e9f980001830bc61d9fcaa64a9 (patch)
tree0bf980c385a61cbc8720cf990762ffc1200f9d6a /examples/qtest/count-strings.test
parent716381f65a2b2dc72f8da2426ba71aeab02c507f (diff)
downloadqpdf-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/count-strings.test')
-rw-r--r--examples/qtest/count-strings.test4
1 files changed, 2 insertions, 2 deletions
diff --git a/examples/qtest/count-strings.test b/examples/qtest/count-strings.test
index ba3f835b..c56d1b62 100644
--- a/examples/qtest/count-strings.test
+++ b/examples/qtest/count-strings.test
@@ -10,8 +10,8 @@ require TestDriver;
my $td = new TestDriver('pdf-count-strings');
$td->runtest("filter tokens",
- {$td->COMMAND => "pdf-count-strings in.pdf"},
- {$td->FILE => "out", $td->EXIT_STATUS => 0},
+ {$td->COMMAND => "pdf-count-strings in.pdf"},
+ {$td->FILE => "out", $td->EXIT_STATUS => 0},
$td->NORMALIZE_NEWLINES);
$td->report(1);