this post was submitted on 31 Aug 2024
207 points (96.8% liked)

Linux

48331 readers
563 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
207
Whats your go-to naming convention? (slrpnk.net)
submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]
158 comments fedilink hide all child comments
 

As far as I know there are these;

  • Camel case = coolFileName
  • Snake case = cool_file_name
  • Kebab case = cool-file-name
  • Pascal case = CoolFileName
  • Dot notation = cool.file.name
  • Flat case = coolfilename
  • Screaming case = COOLFILENAME

Personally I prefer the kebab/dot conventions simply because they allow for easy "navigation" with (ctrl+arrow keys) between each part. What are your preferences when it comes to this? Did I miss any schemes?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 2 months ago (1 children)

Using commands on that is still more annoying, so no way

[–] [email protected] 3 points 2 months ago (2 children)

not really

You can easily escape spaces with \ and my modern shell (fish) suggests and completes filenames for me anyway, so i don't have to type more than the first word in more than 90% of cases.

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago) (1 children)

Typing \ in those cases instead of _ is super annoying.

In my keyboard layout backspace is behind altgr.

[–] [email protected] 1 points 2 months ago (1 children)

the standard keyboard layouts (qwerty, qwertz, etc.) are mostly trash

are there any good alternative keyboard layouts for your native language (finnish if im not mistaken)?

In Germany there is the Neo Family: Neo{,2}, NeoQwert{y,z}, Bone, Mine, ... as well as offsprings of that, but I guess you need your diacritics: å ä and ö. While Neo layouts have these diacritics available, they are made for german, so only ä ö and ü are easily accessible.

[–] [email protected] 1 points 2 months ago

Finnish indeed. I'm not aware of any alternative layouts. å is completely unnecessary for finnish, so maybe the layouts you mentioned could work.

[–] [email protected] 1 points 2 months ago (1 children)

Now do it with a for loop on every file in a dir with thousands of files

[–] [email protected] 1 points 2 months ago (1 children) 
for i in path/to/dir/*
  dosomething_with_my_file $i
end

where is the problem? fish shell doesn't split arguments at spaces

[–] [email protected] 1 points 2 months ago (1 children)

$IFS splits files at spaces

[–] [email protected] 1 points 2 months ago (1 children)

IFS is a special shell variable in bash, ksh and POSIX shells that lets you configure how the shell splits words

by default it splits at spaces tabs and newlines

I use fish a shell that is intentionally not POSIX compatible. While it borrows some principles from Bash and POSIX, it simplifies a lot of things and removes most footguns. Words are split at new lines in fish, which admittedly can also cause troubles, but not nearly as often as in bash and other POSIXy shells.

[–] [email protected] 1 points 2 months ago (1 children)

Wtf why would you intentionally not be POSIX compatible?

[–] [email protected] 1 points 2 months ago

to make a good interactive shell