Linux

48697 readers

1388 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

[email protected]

208

Whats your go-to naming convention? (slrpnk.net)

submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]

155 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] 74 points 3 months ago* (last edited 3 months ago) (4 children)

It depends a bit on the use case. I try to follow naming conventions within specific environments like Python. When just sorting some documents together, I usually do a mix of Kebab and snake case, where I split semantic parts with underscores and connect words with dashes like

2024-08-30_author_document-name_other-important-info.ext

[–] [email protected] 12 points 3 months ago

This is exactly what I do. It lends itself to something like 'prefix_specific-info_version' which is both sortable and easy to read.

[–] [email protected] 7 points 3 months ago* (last edited 3 months ago)

Yeahh that's the best IMO ! But I get most of the time stuck with some testOFtest001 files/directory... cause I'm lazy...

But I always ALWAYS regret it afterward... :/

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

Is something like this defined in a standard somewhere?

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

I can tell that this guy fucks