Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I'm “still afraid to use spaces in file names” years old

twitter.com

Post reply on HN
Print view View original

521–530 of 817 posts

Re: I'm “still afraid to use spaces in file names” years old

#521

Post by daneel_w »

skohan wrote: post #427
daneel_w wrote: post #88

Earlier quoted context omitted.

"On balance I'd rather avoid making a pinky key one of the keys I have to use the most." And you use something else than your pinky finger for the shift key specifically when typing capitalized letters for camelCase?

At least it's where they sit naturally on the keyboard. And the shift key is wider specifically so you don't have to be accurate with your pinky when you're pressing it. The underscore is one of the least ergonomic keys there is. And you need both pinkies to do it

I might be misunderstanding. On all layouts I'm familiar with the underscore key is directly next to one of the shift keys, or left of backspace. Neither layout requires the Vulcan death grip. Shift should always be under your pinky fingers to avoid contortions.

Re: I'm “still afraid to use spaces in file names” years old

#522

Post by nybble41 »

Tempest1981 wrote: post #443
mtift wrote: post #411

I have an overly-aggressive function in my .bashrc to rename all files in the current directory: # Rename all files in a directory rn() { rename "s/ /-/g" * rename "s/_/-/g" * rename "s/–/-/g" * rename "s/://g" * rename "s/\(//g" * rename "s/\)//g" * rename "s/\[//g" * rename "s/\]//g" * rename 's/"//g' * rename "s/'//g" * rename "s/,//g" * rename "y/A-Z/a-z/" * rename "s/---/--/g" * rename "s/-‎--/--/g" * } I use th…

Surely you must run into conflicts now and then?

That's the most beautiful part! After running this script there are no more conflicts, because it just silently overwrites all but one version of the "cleaned" filename.

(Also—that entire function is super inefficient and could be replaced with a single invocation of "rename".)

Re: I'm “still afraid to use spaces in file names” years old

#523

Post by Aulig »

I had to move my development folders because you can't develop Android apps if your project path contains a space. Not sure where the issue is, if it's gradle or something else.

Edit: thinking about it again, it might not have even been the space but the exclamation mark in my path. Or both.

Re: I'm “still afraid to use spaces in file names” years old

#524

Post by marginalia_nu »

gmfawcett wrote: post #295
marginalia_nu wrote: post #238

Earlier quoted context omitted.

I wonder if code to this effect has ever been written before for (int i = 1; i

And that, children, is when marginalia_nu unlocked the seventh circle of the inferno. Tomorrow we'll read the story of how our new demon overlords forced us all back to Windows 3.1.

Got to tweak HIMEM.SYS before the slumbering one can be awakened.

Re: I'm “still afraid to use spaces in file names” years old

#525

Post by curuinor »

Izkata wrote: post #162
pimterry wrote: post #106

I work on a complex desktop application, and it's been astounding the number of bugs that have appeared over the years triggered by spaces and other unusual characters in file names. If you do anything with subprocesses or path processing, it's absurdly easy to hit in a thousand different ways, over and over again. Pro tip: rename your development directory (or even better: the workspace path in CI) to put a space an…

> Pro tip: rename your development directory (or even better: the workspace path in CI) to put a space and/or special characters in it. A former co-worker changed his name in our auth system to include an apostrophe, so that whenever we handled names wrong he'd find it.

the proper name of the glorious sultan of slack, j. r. "bob" dobbs, has the quotation marks and therefore is a great subject for this

Re: I'm “still afraid to use spaces in file names” years old

#526

Post by skohan »

daneel_w wrote: post #521
skohan wrote: post #427

Earlier quoted context omitted.

At least it's where they sit naturally on the keyboard. And the shift key is wider specifically so you don't have to be accurate with your pinky when you're pressing it. The underscore is one of the least ergonomic keys there is. And you need both pinkies to do it

I might be misunderstanding. On all layouts I'm familiar with the underscore key is directly next to one of the shift keys, or left of backspace. Neither layout requires the Vulcan death grip. Shift should always be under your pinky fingers to avoid contortions.

On the US layout it is next to the zero key on the top row.

Re: I'm “still afraid to use spaces in file names” years old

#528

Post by thrwyoilarticle »

JadeNB wrote: post #50
thrwyoilarticle wrote: post #30

Earlier quoted context omitted.

There's a tendency away from snake_case and towards kebab-case in things you interact with via CLI. Even moreso towards nocase. Programs like Powershell eschew ease of use in CLI for readability in scripts.

> Even moreso towards nocase. Nocase (did I break a rule by writing it that way?) seems great when you're enmeshed in the domain and you can see the implicit separators, but then someone looks at your naming from the outside and you're guaranteed to have an 'expertsexchange' in there somewhere.

oh, fsck

Re: I'm “still afraid to use spaces in file names” years old

#529

Post by thrwyoilarticle »

rk06 wrote: post #72
thrwyoilarticle wrote: post #30

Earlier quoted context omitted.

There's a tendency away from snake_case and towards kebab-case in things you interact with via CLI. Even moreso towards nocase. Programs like Powershell eschew ease of use in CLI for readability in scripts.

Powershell is case-insensitive, so camelCase is only a writing preference

It's still verbose in places

Re: I'm “still afraid to use spaces in file names” years old

#530

Post by forgotmypw17 »

Joker_vD wrote: post #223
ori_b wrote: post #113

Earlier quoted context omitted.

So much of computing is dedicated to solving problems that could be omitted.

I mean, that's precisely my thoughts on copyright and licensing in general but what can you realistically do?

Realistically, on an individual scale, you can pretend it doesn't exist and go on with living your life?
Post reply on HN