<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Oct 11, 2015 at 5:22 AM, Harald Hanche-Olsen <span dir="ltr"><<a href="mailto:hanche@math.ntnu.no" target="_blank">hanche@math.ntnu.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Andrew Bernard wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It may be valid, but it is just asking for trouble with many tools and utilities and scripts. Funny, I had to check re UNIX. I have been programming UNIX systems for over thirty years and never even imagined a newline in a filename!<br>
<br>
Would the OP say why he needs to use newlines in filenames? Something best avoided. I suppose this is not a Haskell matter, but one does have to ask.<br>
</blockquote>
<br></span>
The OP must speak for himself, but as far as I am concerned, no reasonable person uses newlines in filenames, ever.<br>
<br>
However, the possibility is there, and it may happen that someone unreasonable has created a filename with a newline in it. This may become a security issue if, for example, someone creates a file named<br></blockquote><div><br></div><div>This is indeed the problem. I'm a sysadmin; if I need a tool like this, I don't usually have any say in what is in the filenames --- and, sadly, people *do* use all manner of odd characters, including newlines, non-UTF8, etc. It's my place to deal with what is, not what would be in an ideal world.</div><div><br></div></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>