this post was submitted on 22 Sep 2025
980 points (98.7% liked)

Programmer Humor

26747 readers
695 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
(page 2) 50 comments
sorted by: hot top controversial new old
[–] jbk@discuss.tchncs.de 8 points 1 week ago (2 children)

smells like skill issue tbh

tools which cant handle being installed/run on directories with spaces are so annoying

[–] vivalapivo@lemmy.today 8 points 1 week ago

tools which cant handle being installed/run on directories with spaces are unacceptably common

[–] nialv7@lemmy.world 3 points 1 week ago (3 children)

You are clearly not a command line user :)

load more comments (3 replies)
[–] lucg@lemmy.world 8 points 2 weeks ago (1 children)

Now I'm imagining a shell that looks iteratively through arguments to find where quotes would make total sense

$ ls
my victims.ods
$ wipe -f my victims.ods --thorough

So the shell would go like

  1. wipe → command name found, ok
  2. -f → no file in the current directory starts with that, skip
  3. my → matches a file, keep in memory...
  4. my victims.ods → full match, but missing quotes!
  5. Prompt user:
Filename "my victims.ods" found without quotes. Choose:
[a]dd quotes this time
[A]lways add quotes (dangerous)
[n]o quotes today please
[N]ever offer adding quotes again
[t]ell me what could possibly go wrong when I choose to always add quotes
[P]unch the person who proposed this feature
[–] BatmanAoD@programming.dev 7 points 2 weeks ago (2 children)

For interactive use, tab-completion essentially makes this a non-issue, because shells add escaping in the appropriate places.

For scripting, where spaces are harder to deal with, unfortunately there's just not much you can do; your two options are basically to learn all of your particular shell's patterns for dealing with whitespace in filenames, or only write scripts in something other than a POSIX shell.

load more comments (2 replies)
[–] BuboScandiacus@mander.xyz 7 points 1 week ago

“_” to the rescue

[–] pineapplelover@lemmy.dbzer0.com 6 points 1 week ago (1 children)
[–] rumba@lemmy.zip 7 points 1 week ago

agreed, "still worth it"

I do, however, tend to keep spaces out of my folder names so i can just use quotes at the end.

/Images/Halloween/Projections/"Creepy Crawlies.mp4"

[–] bitjunkie@lemmy.world 5 points 2 weeks ago

That's what backslash-tab is for

[–] zerofk@lemmy.zip 4 points 1 week ago* (last edited 1 week ago) (1 children)

Computers should just know when I want a space to be part of a file name, and when I want them to be argument separators. No more escaping or quoting.

load more comments (1 replies)
[–] brown567@sh.itjust.works 4 points 2 weeks ago

whitespaceIsTheEnemy

[–] kieron115@startrek.website 4 points 1 week ago

at least you/arent/using\ linux

[–] Korne127@lemmy.world 2 points 1 week ago

Can't relate. I use shell all the time, and I always use spaces in file paths, especially to make sure scripts I make still work then

load more comments
view more: ‹ prev next ›