Skip Navigation
Linux @lemmy.ml Sunny' 🌻 @slrpnk.net

Whats your go-to naming convention?

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?

158

You're viewing part of a thread.

Show Context
158 comments
  • for i in path/to/dir/*
  dosomething_with_my_file $i
end

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

    • $IFS splits files at spaces

      • 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.

You've viewed 158 comments.