this post was submitted on 09 Apr 2024
133 points (94.6% liked)
Programming
17398 readers
96 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've run into bizarre behavior with windows command lines plenty of times before, but I'd never put all the pieces together and realized that:
a) windows really does pass around unadorned monolithic strings containing the entire command line of an executed command, and
b) there's no parsing standard for command lines in windows
sigh, windows