I very intentionally have all my code in Personal Projects 🥰 and Work Projects 🏦 directories so I can find bugs in the handling of file paths.
not sure why the default behavior is this:
file\ name\ with\ a\ bunch\ of\ spaces
instead of this:
"file name with a bunch of spaces"
but you can just press " before pressing tab to auto-complete, and it will use the 2nd form
Because quoting requires token expansion (e.g. ~ to /home/you). Escaping gives you a much shorter path in that case.
That said I'm with you, full quoted paths read better to me.
My work has me working with Matlab Simulink paths, which may (and sometimes actually do) contain newlines.
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
i y'all just started using fish shell, you'd have proper shell completions and argument splitting that doesn't care about spaces in file names
at least you/arent/using\ linux
I still use spaces
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"
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.
The number of keystrokes needed to type an underscore is the same that you need to type backslash space, so I don't see how underscores are in improvement
capital letters.
Microsoft intentionally made programs install to C:\Program Files on Windows 95+ to force programmers to deal with spaces in filenames.
Someone make one of those "statements made by the utterly deranged" memes about it, please and thank you.
what is even more funny about this is that the name of that directory used to be locale-dependent, so in sweden it was just called "Program", completely nullifying that idea.
C:\Program Files
C:\Program Files (x86)
C:\ProgramData
C:\PROGRA~1
The fucking parenthetical x86 absolutely kills me. I don't normally wish dick cancer on people,
I've recently learned that in Linux, you can use emois in filenames. I died a ~~little~~ lot inside when I learned that.
On Linux file systems you can use any character except NULL, and / is a reserved character.
E.g. on ext-4 "All characters and character sequences permitted, except for NULL ('\0'), '/', and the special file names "." and ".." which are reserved for indicating (respectively) current and parent directories."
I once accidentally created a file with a newline character in it... it was pretty tricky to fix from command line.
I\ don\'t\ know\ what\ you\ mean,\ I\'ve\ never\ encountered\ any\ annoyances.
'I don\'t know what you mean, I\'ve never encountered any annoyances.'
Single quotes don't allow any escaping in shell, you need
'I don'\''t know what you mean, I'\''ve never encountered any annoyances'
Or, in Zsh with setopt rcquotes:
'I don''t know what you mean, I''ve never encountered any annoyances'
Oh right, good catch. That's me shell scripting while in a meeting. 🫠
Good use of a meeting to be fair
it works in fish
Oh\ come\ on,\ it\'s\ not\ that\ bad
Some shells enclose those types of files within inverted commas. Such that:
> ls
file\ name.md
is instead
> ls
'file name.md'
(I use fish)
Are you typing the whole filename by hand? Tab expansion exists, you know?
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.