fix spacecheck nits (#570)

vszakats · web-flow · commit 2fb7187ee893 · 2025-11-05T23:15:19.000+01:00
Verified OK to not change PDF output.
diff --git a/LICENSE b/LICENSE
@@ -33,7 +33,7 @@ exhaustive, and do not form part of our licenses.
      material not subject to the license. This includes other CC-
      licensed material, or material used under an exception or
      limitation to copyright. More considerations for licensors:
-	wiki.creativecommons.org/Considerations_for_licensors
+        wiki.creativecommons.org/Considerations_for_licensors
 
      Considerations for the public: By using one of our public
      licenses, a licensor grants the public permission to use the
@@ -49,8 +49,8 @@ exhaustive, and do not form part of our licenses.
      such as asking that all changes be marked or described.
      Although not required by our licenses, you are encouraged to
      respect those requests where reasonable. More_considerations
-     for the public: 
-	wiki.creativecommons.org/Considerations_for_licensees
+     for the public:
+        wiki.creativecommons.org/Considerations_for_licensees
 
 =======================================================================
 
@@ -393,4 +393,3 @@ the avoidance of doubt, this paragraph does not form part of the
 public licenses.
 
 Creative Commons may be contacted at creativecommons.org.
-
diff --git a/Makefile b/Makefile
@@ -8,13 +8,13 @@ $(OUT): mkindex.pl Makefile index-words $(IMDS)
 	@echo "generates $(OUT)"
 	@perl mkindex.pl $(IMDS) > $(OUT)
 
-mdcheck: 
+mdcheck:
 	@./checkmd $(MDS)
 
-check: 
+check:
 	@proselint $(MDS)
 
-wordcheck: 
+wordcheck:
 	@./mgrep $(MDS)
 
 fixup:
diff --git a/README.md b/README.md
@@ -8,7 +8,7 @@ reports and why millions of existing users use it.
 
 This book is meant to be interesting and useful to both casual readers and
 somewhat more experienced developers. It offers something for everyone to pick
-and choose from. 
+and choose from.
 
 Do not read this book from front to back. Read the chapters or content you are
 curious about and flip back and forth as you see fit.
diff --git a/build/cmake.md b/build/cmake.md
@@ -27,4 +27,3 @@ To create a subdirectory for the build and run make in there:
     cd build
     cmake ..
     make
-
diff --git a/build/separate.md b/build/separate.md
@@ -59,7 +59,7 @@ It can look like this when you have installed your new curl build in
 
     export LD_LIBRARY_PATH=$HOME/install/lib
     $HOME/install/bin/curl https://example.com/
-    
+
 ### `rpath`
 
 Often, a better way to forcibly load your separate libcurl instead of the
diff --git a/checkmd b/checkmd
@@ -29,7 +29,6 @@ sub check {
             }
         }
 
-        
         if($next_line_should_be_blank) {
             if(! ($line =~ m/^[\s]*$/)) {
                 error($f, $line, $l, "The line after a '#' header should be blank.");
diff --git a/cmdline/configfile.md b/cmdline/configfile.md
@@ -42,10 +42,10 @@ Enter one command per line. Use a hash symbol for comments:
 
 ## Command line options
 
-You can use both short and long options, exactly as you would write them on a command line. 
+You can use both short and long options, exactly as you would write them on a command line.
 
 You can also write the long option WITHOUT the leading two dashes to make
-it easier to read. 
+it easier to read.
 
     # curl config file
 
@@ -58,7 +58,7 @@ it easier to read.
 ## Arguments
 
 A command line option that takes an argument must have its argument provided on
-the SAME LINE as the option. 
+the SAME LINE as the option.
 
     # curl config file
 
diff --git a/cmdline/curlver.md b/cmdline/curlver.md
@@ -18,7 +18,7 @@ An example output from a Debian Linux in June 2020:
     libssh2/1.8.0 nghttp2/1.41.0 librtmp/2.3
     Release-Date: 2020-01-08
     Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3
-    pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
+    pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
     Features: AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos
     Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets
 
@@ -30,7 +30,7 @@ looks like:
     Protocols: dict file ftp ftps http https imap imaps pop3 pop3s smtp smtps
     telnet tftp
     Features: AsynchDNS IPv6 Largefile SSPI Kerberos SPNEGO NTLM SSL
-    
+
 The meaning of the four lines?
 
 ## Line 1: curl
diff --git a/cmdline/urls/scheme.md b/cmdline/urls/scheme.md
@@ -53,7 +53,7 @@ default to HTTP.
 For example, this gets a file from an FTP site:
 
     curl ftp.funet.fi/README
-    
+
 While this gets data from an HTTP server:
 
     curl example.com
diff --git a/cmdline/variables.md b/cmdline/variables.md
@@ -66,7 +66,7 @@ Insert `{{` verbatim in the string by escaping it with a backslash:
 
 In the example below, the variable `host` is set and then expanded:
 
-    curl \ 
+    curl \
         --variable host=example \
         --expand-url "https://{{host}}.com"
 
@@ -87,7 +87,7 @@ As an example, assign the `%USER` environment variable to a curl
 variable and insert it into a URL. Because no default value is specified, this
 operation fails if the environment variable does not exist:
 
-    curl \ 
+    curl \
         --variable %USER \
         --expand-url "https://example.com/api/{{USER}}/method"
 
@@ -136,7 +136,7 @@ These functions are available: `trim`, `json`, `url` and `b64`
 
 ## Function: `trim`
 
-Expands the variable without leading and trailing white space. White space is defined as: 
+Expands the variable without leading and trailing white space. White space is defined as:
 
 * horizontal tabs
 * spaces
@@ -180,7 +180,7 @@ Expands the variable base64 encoded. Base64 is an encoding for binary data
 that only uses 64 specific characters.
 
     --expand-data "content={{value:b64}}"
-    
+
 To trim the variable first, apply both functions (in this order):
 
     --expand-data "content={{value:trim:b64}}"
diff --git a/firsttbd.sh b/firsttbd.sh
@@ -1,3 +1,2 @@
 #!/bin/sh
 grep -c "^TBD" README.md `grep -o '[a-z0-9/-]*\.md' SUMMARY.md`  | grep -v :0 | head -n1
-
diff --git a/ftp/dirlist.md b/ftp/dirlist.md
@@ -20,4 +20,3 @@ the special formatting of the regular directory listings is to tell curl to
 
 NLST has its own quirks though, as some FTP servers list only actual *files*
 in their response to NLST; they do not include directories and symbolic links.
-
diff --git a/ftp/twoconnections.md b/ftp/twoconnections.md
@@ -56,4 +56,3 @@ Using either active or passive transfers, any existing firewalls in the
 network path pretty much have to have stateful inspection of the FTP traffic
 to figure out the new port to open that up and accept it for the second
 connection.
-
diff --git a/helpers/url/get-part.md b/helpers/url/get-part.md
@@ -10,25 +10,25 @@ pass a pointer to such a variable.
 
     char *host;
     rc = curl_url_get(h, CURLUPART_HOST, &host, 0);
-    
+
     char *scheme;
     rc = curl_url_get(h, CURLUPART_SCHEME, &scheme, 0);
-    
+
     char *user;
     rc = curl_url_get(h, CURLUPART_USER, &user, 0);
-    
+
     char *password;
     rc = curl_url_get(h, CURLUPART_PASSWORD, &password, 0);
-    
+
     char *port;
     rc = curl_url_get(h, CURLUPART_PORT, &port, 0);
-    
+
     char *path;
     rc = curl_url_get(h, CURLUPART_PATH, &path, 0);
-    
+
     char *query;
     rc = curl_url_get(h, CURLUPART_QUERY, &query, 0);
-    
+
     char *fragment;
     rc = curl_url_get(h, CURLUPART_FRAGMENT, &fragment, 0);
 
diff --git a/helpers/ws/meta.md b/helpers/ws/meta.md
@@ -37,7 +37,7 @@ This is binary data.
 
 This is the final fragment of the message, if this is not set, it implies that
 there is another fragment coming as part of the same message.
- 
+
 ### `CURLWS_CLOSE`
 
 This transfer is now closed.
diff --git a/helpers/ws/read.md b/helpers/ws/read.md
@@ -28,7 +28,7 @@ The `curl_ws_recv` function has this prototype:
                           size_t *recv, struct curl_ws_frame **meta);
 
 `curl` - the handle to the transfer
- 
+
 `buffer` - pointer to a buffer to receive the WebSocket data in
 
 `buflen` - the size in bytes of the **buffer**
diff --git a/http/browserlike.md b/http/browserlike.md
@@ -136,4 +136,3 @@ environment and most likely is different from those of browsers. Curl's CLI
 does not have options to change all the various parts of the fingerprint,
 however an advanced user can customize the fingerprint through the use of
 libcurl and by compiling curl from source themselves.
-
diff --git a/http/cookies/engine.md b/http/cookies/engine.md
@@ -17,4 +17,3 @@ cookies it received. Assuming the site in this example would set cookies and
 then do a redirect we would do:
 
     curl -L -b "" http://example.com
-
diff --git a/http/cookies/reading.md b/http/cookies/reading.md
@@ -17,4 +17,3 @@ Remember that this only *reads* from the file. If the server would update the
 cookies in its response, curl would update that cookie in its in-memory store
 but then eventually throw them all away when it exits and a subsequent invocation
 of the same input file would use the original cookie contents again.
-
diff --git a/http/cookies/writing.md b/http/cookies/writing.md
@@ -18,4 +18,3 @@ When curl writes cookies to this file, it saves all known cookies including
 those that are session cookies (without a given lifetime). curl itself has no
 notion of a session and it does not know when a session ends so it does not
 flush session cookies unless you tell it to.
-
diff --git a/http/https.md b/http/https.md
@@ -8,4 +8,3 @@ See the [Using TLS](../usingcurl/tls.md) section for in-depth details on how
 to modify and tweak the TLS details in an HTTPS transfer.
 
 * [HSTS](https/hsts.md)
-
diff --git a/http/modify/headers.md b/http/modify/headers.md
@@ -34,4 +34,3 @@ side of the colon (which is a rare thing), the magic marker for that is to
 instead end the header field name with a *semicolon*. Like this:
 
     curl -H "Empty;" http://example.com
-
diff --git a/http/modify/method.md b/http/modify/method.md
@@ -29,4 +29,3 @@ on the option so you should only rarely have to explicitly ask for it with
 `-X`. It should also be noted that when curl follows redirects like asked to
 with `-L`, the request method set with `-X` is sent even on the subsequent
 redirects.
-
diff --git a/http/post/browsersends.md b/http/post/browsersends.md
@@ -14,4 +14,3 @@ you cannot see form submissions in clear text on the wire but instead you need
 to make sure you can have Wireshark extract your TLS private key from your
 browser. See the [SSLKEYLOGFILE section](../../usingcurl/tls/sslkeylogfile.md)
 for details on doing that.
-
diff --git a/http/post/json.md b/http/post/json.md
@@ -19,9 +19,9 @@ Send a basic JSON object to a server:
 Send JSON from a local file:
 
     curl --json @json.txt https://example.com/
-    
+
 Send JSON passed to curl on stdin:
-    
+
     echo '{"a":"b"}' | curl --json @- https://example.com/
 
 You can use multiple `--json` options on the same command line. This makes
diff --git a/install/linux.md b/install/linux.md
@@ -74,11 +74,11 @@ In order to install command-line tool:
 
 ## Arch Linux
 
-curl is located in the core repository of Arch Linux. This means it should be 
+curl is located in the core repository of Arch Linux. This means it should be
 installed automatically if you follow the normal installation procedure.
 
 If curl is not installed, Arch Linux uses `pacman` to install packages:
-    
+
     pacman -S curl
 
 ## SUSE and openSUSE
diff --git a/install/macos.md b/install/macos.md
@@ -6,7 +6,7 @@ project, we recommend installing [homebrew](https://brew.sh/) (a macOS
 software package manager) and then install the curl package from them:
 
     brew install curl
-    
+
 Note that when installing curl, brew does not create a `curl` symlink
 in the default homebrew folder, to avoid clashes with the macOS version of curl.
 
diff --git a/libcurl-http/cookies.md b/libcurl-http/cookies.md
@@ -140,4 +140,3 @@ separated with TAB characters.
 | 4     | 1462299217  | Expires at – seconds since Jan 1st 1970, or 0 |
 | 5     | person      | Name of the cookie                            |
 | 6     | daniel      | Value of the cookie                           |
-
diff --git a/libcurl/curlcode.md b/libcurl/curlcode.md
@@ -21,4 +21,3 @@ then libcurl stores a related error message there before it returns an error:
 
     char error[CURL_ERROR_SIZE]; /* needs to be at least this big */
     CURLcode ret = curl_easy_setopt(handle, CURLOPT_ERRORBUFFER, error);
-
diff --git a/libcurl/globalinit.md b/libcurl/globalinit.md
@@ -17,4 +17,3 @@ did not do it before any actual file transfer starts) and it then uses its own
 defaults. Beware that it is still not thread safe even then, so it might cause
 some "interesting" side effects for you. It is much better to call
 curl_global_init() yourself in a controlled manner.
-
diff --git a/libcurl/headers.md b/libcurl/headers.md
@@ -8,4 +8,3 @@ That file in turn includes a few other public header files but you can pretend
 they do not exist. (Historically speaking, we started out slightly different
 but over time we have stabilized around this form of only using a single one
 for includes.)
-
diff --git a/pdf.txt b/pdf.txt
@@ -13,4 +13,3 @@ geometry:
 - bottom=2cm
 classoption: openany       # disable empty pages in PDF
 ---
-
diff --git a/project/bugs.md b/project/bugs.md
@@ -4,7 +4,7 @@ The development team does a lot of testing. We have a whole test suite that is
 run frequently every day on numerous platforms in order to exercise all
 code and make sure everything works as expected.
 
-Still, there are times when things do not work the way they should, and we 
+Still, there are times when things do not work the way they should, and we
 depend on people reporting it to us.
 
 ## A bug is a problem
@@ -19,11 +19,11 @@ to? That is a problem and we should fix it.
 
 This may sound easy and uncomplicated but is a fundamental truth in our and
 other projects. Just because it is an old project and has thousands of users
-does not mean the development team knows about the problem you just stumbled 
+does not mean the development team knows about the problem you just stumbled
 into. Maybe users have not paid attention to details as much as you have, or
 perhaps it just never triggered for anyone else.
 
-We rely on users experiencing problems to report them. We need to know of 
+We rely on users experiencing problems to report them. We need to know of
 their existence in order to fix them.
 
 ## Fixing the problems
@@ -53,16 +53,16 @@ GitHub](https://github.com/curl/curl/issues).
 
 Testing software thoroughly and properly is a lot of work. Testing software
 that runs on dozens of operating systems and CPU architectures, with
-server implementations which have their own sets of bugs and interpretations 
+server implementations which have their own sets of bugs and interpretations
 of the specs, is even more work.
 
-The curl project has a test suite that iterates over all existing test cases, 
-runs each test and verifies that the outcome is correct and that no other 
+The curl project has a test suite that iterates over all existing test cases,
+runs each test and verifies that the outcome is correct and that no other
 problem happened, such as a memory leak or something fishy in the protocol layer.
 
-The test suite is meant to be run after you have built curl yourself. There are 
-a number of volunteers who also help out by running the test suite 
-automatically a few times per day to make sure the latest commits are tested. 
+The test suite is meant to be run after you have built curl yourself. There are
+a number of volunteers who also help out by running the test suite
+automatically a few times per day to make sure the latest commits are tested.
 This way we discover the worst flaws not long after their introduction.
 
 We do not test everything, and even when we try to test things there are
diff --git a/protocols/http.md b/protocols/http.md
@@ -1,5 +1,5 @@
 # HTTP basics
- 
+
 HTTP is a protocol that is easy to learn the basics of. A client connects to a
 server—and it is always the client that takes the initiative—sends a
 request and receives a response. Both the request and the response consist of
diff --git a/source/options.md b/source/options.md
@@ -30,4 +30,3 @@ Both TLS handling and name resolving are handled with an internal API that
 hides the specific implementation and choice of 3rd party software
 library. That way, most of the internals work the same independent of which
 TLS library or name resolving system libcurl is told to use.
-
diff --git a/source/style.md b/source/style.md
@@ -264,4 +264,3 @@ of identifying them:
        size_t way_to_write;
     } something;
     something instance;
-
diff --git a/transfers/callbacks/read.md b/transfers/callbacks/read.md
@@ -28,4 +28,3 @@ return a few "magic" return codes to cause libcurl to return failure
 immediately or to pause the particular transfer. See the [CURLOPT_READFUNCTION
 man page](https://curl.se/libcurl/c/CURLOPT_READFUNCTION.html) for
 details.
-
diff --git a/transfers/callbacks/write.md b/transfers/callbacks/write.md
@@ -83,6 +83,6 @@ You implement the callback in a manner similar to:
 
       /* we pass our 'chunk' to the callback function */
       curl_easy_setopt(curl_handle, CURLOPT_WRITEDATA, (void *)&chunk);
-    
+
       free(chunk.memory);
     }
diff --git a/transfers/drive/easy.md b/transfers/drive/easy.md
diff --git a/uni.pl b/uni.pl
diff --git a/usingcurl/connections/name.md b/usingcurl/connections/name.md
diff --git a/usingcurl/connections/timeout.md b/usingcurl/connections/timeout.md
diff --git a/usingcurl/downloads/browsers.md b/usingcurl/downloads/browsers.md
diff --git a/usingcurl/downloads/content-disp.md b/usingcurl/downloads/content-disp.md
diff --git a/usingcurl/downloads/raw.md b/usingcurl/downloads/raw.md
diff --git a/usingcurl/downloads/retry.md b/usingcurl/downloads/retry.md
diff --git a/usingcurl/proxies/auth.md b/usingcurl/proxies/auth.md
diff --git a/usingcurl/proxies/env.md b/usingcurl/proxies/env.md
diff --git a/usingcurl/tls/clientcert.md b/usingcurl/tls/clientcert.md
diff --git a/usingcurl/tls/enable.md b/usingcurl/tls/enable.md
diff --git a/usingcurl/tls/versions.md b/usingcurl/tls/versions.md
diff --git a/usingcurl/transfers/request-rate.md b/usingcurl/transfers/request-rate.md
diff --git a/usingcurl/transfers/tooslow.md b/usingcurl/transfers/tooslow.md

Original file line number	Diff line number	Diff line change
`@@ -29,7 +29,6 @@ sub check {`
`29`	`29`	`}`
`30`	`30`	`}`
`31`	`31`
`32`		`-`
`33`	`32`	`if($next_line_should_be_blank) {`
`34`	`33`	`if(! ($line =~ m/^[\s]*$/)) {`
`35`	`34`	`error($f, $line, $l, "The line after a '#' header should be blank.");`