Add documentation of how to use backslash escapes.

[tmccombs]

See #102

[emersion]

TBH this seems out of place for the man page.

[tmccombs]

I agree with @subnut that the current text is a little misleading on how slurp handles \n, and it would probably be good to direct users on how to add newlines to a custom format string.

Do you have a better solution?

I suppose some other options are to always add a newline to the end of the output or to add a "%n" escape code to add a newline.

[columbarius]

Alternative: Adding this at least to the README.md file, which already contains some examples?

[emersion]

My guess is that it doesn't really matter whether there's a newline or not, read(1) and getline(3) should still behave properly when there's no final newline. The fact that the default format includes a final newline is just a nicety to have slightly better output when the user manually invokes slurp (avoid having the shell prompt on the same line).

slurp's man page is not a good place to explain how to use a shell, especially when it's Bash specific.

I'd just change the man page to e.g.

The default format is "%x,%y %wx%h" followed by a newline.

[tmccombs]

I've removed the shell specific note from the man page, and instead added an example to the README.