title: How to find files containing newlines in their names
body: <p>There is so much told about correct handling of file names which <a href="http://mywiki.wooledge.org/ParsingLs" rel="nofollow">contain weird symbols like newlines</a>. I thought using IFS set to newline would solve the issue in general except obviously for the case if one has a name with newline in it. So as a means of defense script could check at first whether a subtree has at least one file with newline and stop with a message to fix the name first.
  Surprisingly I couldn't make <code>find</code> doing that with <code>-regex</code> match. Only way successful was a rather ugly</p>
  
  <pre><code>find . -name "*"$'\n'"*"
  </code></pre>
  
  <p>But for example <code>find . -regex ".*\n.*"</code> does not work. Emacs regex should allow escape characters like \n, shouldn't it ? Interestingly that it matches another file with character <code>n</code> in the name. Experimented with different -regextypes only to find that types <code>awk</code> <code>sed</code> <code>posix-extended</code> and some more would match file with a newline (let's say <code>a\nxxx</code>) but in addition they will match files with character <code>n</code> as well. Weird.
  On other hand GNU find documentation does not tell anything about support of escaped characters like <code>\n</code>. Are they really not supported so we can't use <code>\t \n \r \a</code> and similar in find regexps ?</p>