Malle_Yeno

The rust compiler holds your hand, wraps you in blankets, makes you hot chocolate, kisses you on the forehead before it gently and politely points out what you did wrong and how you can solve it step-by-step. It would never think of something as heinous as swearing at you, shame on you for insulting my wife’s honour like this.

Mixing tabs and white spaces in 2024 is categorically a you problem lmao

Hey thanks for this! I used f droid for a while but was always meh on the UI and how clunky it is. I used this for a bit and I already like it waaaay more. Cheers!

I might be already exposing myself as an emacs user, but I think Lisp naming convention is pretty reasonable. I use it in other languages as far as their language rules allow me

• if a variable or function is a predicate (as in if it tests if something is true or not), append p or _p/-p

• variables and functions both have lisp case variable-name-here. Sub for _ in languages that dont allow - in names

• unused or unexposed variables are prefixed _ .

• top level packages get naming rights. So if I’m making cool-package then variables or functions that are specific to it are cool-package-variable (especially if it is exposed to other packages). cool-package/variable is also good if allowed.

• otherwise, separate namespaces with /. So there’s main-function and my/main-function. If / is reserved, then I assume the language has a way of segmenting namespaces already and just default to that since _ or - would get ambiguous here.

See the rest here: https://github.com/bbatsov/emacs-lisp-style-guide