What is the meaning of read -r?

In order to understand another answer (by glenn jackman):

find / -type d -print0 | while read -r -d '' dir; do ls -ltr "$dir" | sed '$!d'; done

the first step is to understand the usage of the option -r of the read command.

First, I thought, it would be sufficient to simply execute

man read

to look up the meaning of the -r option, but I realized the man page does not contain any explanation for options at all, so I Googled for it. 
I got some read -t, read -p examples, but no read -r.

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

There is no stand-alone read command: instead, it is a shell built-in, and as such is documented in the man page for bash:

read [-ers] [-a aname] [-d delim] [-i text] [-n nchars] [-N nchars] [-p prompt] [-t timeout] [-u fd] [name ...]

    ︙
-r
Backslash does not act as an escape character. 
The backslash is considered to be part of the line. 
In particular, a backslash-newline pair may not be used as a line
continuation.

So, to summarize, read normally allows long lines to be broken using a trailing backslash character, and normally reconstructs such lines. This slightly surprising behavior can be deactivated using -r.

Method 2

The -r option prevents backslash escapes from being interpreted. Here’s an example:

Assume there’s a file with this content:

ngRTM6hNqgziZcqCcEJN7bHAP9a1GeMs
Ni3EAX1qvogWpRIPE3oagJL6nwlQQW9y
bjJHyaVBrUcyZOY5U4h9QHnpEPqg\\\\Q9Fk
iNOvAyBTAcN5n1uwR4GvRfAGUbPWiXaxn
cqGPPStH3gaWolrfVAlMtoWiSuLa7GzQnnn
EnO04N1nEkpWbfXRxrtYNqCZDpFtrQIXS

$ while read line; do echo $line; done < tempfile
ngRTM6hNqgziZcqCcEJN7bHAP9a1GeMsNi3EAX1qvogWpRIPE3oagJL6nwlQQW9y
bjJHyaVBrUcyZOY5U4h9QHnpEPqg\\Q9Fk
iNOvAyBTAcN5n1uwR4GvRfAGUbPWiXaxn
cqGPPStH3gaWolrfVAlMtoWiSuLa7GzQnnn
EnO04N1nEkpWbfXRxrtYNqCZDpFtrQIXS

$ while read -r line; do echo $line; done < tempfile
ngRTM6hNqgziZcqCcEJN7bHAP9a1GeMs
Ni3EAX1qvogWpRIPE3oagJL6nwlQQW9y
bjJHyaVBrUcyZOY5U4h9QHnpEPqg\\\\Q9Fk
iNOvAyBTAcN5n1uwR4GvRfAGUbPWiXaxn
cqGPPStH3gaWolrfVAlMtoWiSuLa7GzQnnn
EnO04N1nEkpWbfXRxrtYNqCZDpFtrQIXS

Method 3

The Bash man page’s section about read states that, by default…

The backslash character
() may be used to remove any special meaning for the next character read and for line continuation.

but, if you pass -r, then

Backslash does not act as an escape character. 
The backslash is considered to be part of the line. 
In particular, a backslash-newline pair may not then be used as a line continuation.

A little thought suggests that the only possible “special meaning” they could be talking about is the character serving as a delimiter. And sure enough, without -r, you can backslash-escape a delimiter or a newline, but with -r, you can’t, and backslashes just get interpreted as literal backslashes:

$ <i>read -d 'x'    var1 <<< 'There was once 
a curious Unix user.xHe did a little test.'</i>
$ <i>echo "$var1"</i>
There was once a curious Unix user.
$ <i>read -d 'x' <b>-r</b> var2 <<< 'There was once 
a curious Unix user.xHe did a little test.'</i>
$ <i>echo "$var2"</i>
There was once 
a curious Uni

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0