You must log in or # to comment.
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. 🫠
not sure why the default behavior is this:
file\ name\ with\ a\ bunch\ of\ spacesinstead 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 formI very intentionally have all my code in
Personal Projects 🥰andWork Projects 🏦directories so I can find bugs in the handling of file paths.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
Don’t try svelte kit. This is pseudocode but it’s valid. The only symbol show here that is not real is the / that I’ve placed at the end of folder to show that they are folders. There are other special cases
routes/ +page.ts (admin)/ +page.ts [user=uuid]/ [[community]]/ +page.ts posts/ [...postIds@]/ +page.tssveltekit is beautiful (thanks for spreading the word)
Im trying it out yet. It seems fun, the tutorial is amazing. I don’t think I’d want to do large enterprise projects with it
Have you noticed issues that you think would arrise at scale, etc for an enterprise project?
I’m using it for a small/medium sized project and it’s great and has not got in the way once. Wondering how you feel, since I don’t have experience with much enterprise code.
Oh. No. You win. Mine is a gut feeling that modeling all routes with folders would become a paid. To navigate and manage, while you have actual experience
smells like skill issue tbh
tools which cant handle being installed/run on directories with spaces are so annoying
tools which cant handle being installed/run on directories with spaces are unacceptably common
You are clearly not a command line user :)
I vaguely remember
zshin Manjaro (by default) having a tab completion that automatically added the slashes.
Never set it up myself though.But I really hate having to worry about quoting my file variables in scripts.
So much, that after a certain complexity, I just give up the script and make the thing in C++.
Oh, and if I make a script that doesn’t handle file names properly (because it’s not required in that specific use case), I make sure to delete it after use, to prevent mistaken use later, which would otherwise cause more headache than just having to rewrite a script.
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”
the struggle between spaces in filenames look cute and oh fuck what’s the code to reference a space in a filename in terminal?
Just put the whole thing in quotes. You might have to escape extra sets of quotes, usually with a backslash.
Or you can also put a
\in front of the spaceIf you intend on using that with tab completions, you will have extra work to do.
Some shells put the path in quotes automatically as you attempt to complete anything with spaces in it.
Yeah, just need to set it up correctly.
“_” to the rescue
My work has me working with Matlab Simulink paths, which may (and sometimes actually do) contain newlines.
at least you/arent/using\ linux
Mv /home/“$USER”/Downloads /home/“$USER”/downloads
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.
capital letters.
deleted by creator
