892

I_fucking_hate_them_now (media.piefed.world)

submitted 10 months ago by cm0002@piefed.world to c/programmer_humor@programming.dev

140 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] xthexder@l.sw0.com 54 points 10 months ago

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

[-] malware@lemmy.zip 78 points 10 months ago

[-] tdawg@lemmy.world 62 points 10 months ago

Arrest this person

[-] voodooattack@lemmy.world 29 points 10 months ago

This is absolutely haram

[-] malware@lemmy.zip 23 points 10 months ago

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

[-] voodooattack@lemmy.world 9 points 10 months ago

I once made a script to delete .o, .lib, and .so files from my huge dev folder to free up space on my home partition.

It did not go as planned.

[-] Jeremyward@lemmy.world 7 points 10 months ago

O no, o no no no

[-] exu@feditown.com 13 points 10 months ago

This is why you shouldn't parsels output btw. Use find and read instead

[-] GenderNeutralBro@lemmy.sdf.org 13 points 10 months 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.

[-] sukhmel@programming.dev 6 points 10 months ago

I created a file with backspace in name, it was hard to understand why filename doesn't match

[-] toynbee@lemmy.world 4 points 10 months ago

I don't conduct interviews very often, but when I do, one of my questions is always about interacting with files that have special characters in the filename.

[-] Warl0k3@lemmy.world 3 points 10 months ago* (last edited 10 months ago)

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

[-] xthexder@l.sw0.com 2 points 10 months 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.