Yeah, my attempt to write a double backslash turned iinto a single backslash in the presented comment!

Your double backslash should be fine. Techically '\e' is more correct, but double backslash should only fail on versions of [nt]roff that have been obsolete for so long you probably weren't born yet when they were end-of-lifed :-)

---
** [bugs:#1234] libcurl_tutorial.3 contains incorrect backslash**
**Status:** closed-fixed
**Created:** Tue May 28, 2013 11:28 AM UTC by Eric S. Raymond
**Last Updated:** Mon Jun 03, 2013 08:56 PM UTC
**Owner:** Daniel Stenberg
--- libcurl-tutorial.3-unpatched	2013-05-28 07:24:46.577949934 -0400
+++ libcurl-tutorial.3	2013-05-28 07:25:06.161949568 -0400
@@ -1246,7 +1246,7 @@
 could also use CURLINFO_EFFECTIVE_URL to generate a file name from a
 server-supplied redirect URL. Special care must be taken to sanitize such
 names to avoid the possibility of a malicious server supplying one like
-"/etc/passwd", "\autoexec.bat" or even ".bashrc".
+"/etc/passwd", "autoexec.bat" or even ".bashrc".
 
 .IP "Server Certificates"
 A secure application should never use the CURLOPT_SSL_VERIFYPEER option to
---
Sent from sourceforge.net because you indicated interest in <https://sourceforge.net/p/curl/bugs/1234/>
To unsubscribe from further messages, please visit <https://sourceforge.net/auth/subscriptions/>