Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • To save us searching, could you add a list of which ones were missed? Commented Mar 4, 2019 at 16:36
  • @StéphaneChazelas your title edit grossly deviates from the original intent and is misleading, since the characters removed are not random, but always from the start of the path, which suggest that read had bit more than it could chew, probably confused by length in bytes vs length in characters (that ó from Edición is probably the culprit). Commented Mar 4, 2019 at 17:17
  • @UncleBilly, 0, 4, 5, 6, 7 or 8 bytes are being removed seemingly randomly from the start of each line of the output of find (with no observable relation between that number and the number of non-ASCII characters in those lines). bash's read has no limit on the size of the line it reads (like in any Bourne-like shell). It reads one byte at a time until it finds a newline, it only needs to decode bytes as characters for the IFS processing here, but that happens after the finding of the line delimiter. Commented Mar 4, 2019 at 17:31
  • @StéphaneChazelas not from the start of each line; only from some lines -- I may be actually on the wrong path, but I don't see anything like Overwrite ? [y/N] from ffmpeg in the OP's output (which should've appeared if ffmpeg was trying to read from stdin), and I vaguely remember a similar bug with bash's read` reading too much. Commented Mar 4, 2019 at 17:34
  • @UncleBilly, note the 0 in my list of numbers ;-) Commented Mar 4, 2019 at 17:34