you are viewing a single comment's thread
view the rest of the comments
[–] 54 points 1 year ago (14 children)

I once accidentally created a file with a newline character in it... it was pretty tricky to fix from command line.

  • source
  • parent
  • hideshow 14 child comments
  • [–] 78 points 1 year ago (6 children)
  • [–] 29 points 1 year ago (3 children)
  • [–] 23 points 1 year ago (2 children)

    it was on accident, habibi, I swear 😁. I messed up some cmake code for preprocessing .txt ascii sprites into constants and accidentally created this abomination

  • source
  • parent
  • hideshow 2 child comments
  • [–] 13 points 1 year ago

    I actually did this a lot on classic Mac OS. Intentionally.

    The reason was that you could put a carriage return as the first character of a file, and it would sort above everything else by name while otherwise being invisible. You just had to copy the carriage return from a text editor and then paste it into the rename field in the Finder.

    Since OS X / macOS can still read classic Mac HFS+ volumes, you can indeed still have carriage returns in file names on modern Macs. I don't think you can create them on modern macOS, though. At least not in the Finder or with common Terminal commands.

  • source
  • parent
  • [–] 3 points 1 year ago* (3 children)

    Did you not just use tab? That's the usual method of dealing with weird characters in filenames that I've found

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 year ago

    This was quite a while ago now, but I don't think my shell escaped the tab complete properly, I remember it just printing a literal newline and evaluating it as a second command. I think there was other unicode in there too, otherwise I would have just typed it out. I had to do something with null terminated output and piping it in to mv, but I can't remember what exactly.

  • source
  • parent