Furry artist and streamer - malleyeno.com
That section does not describe how it does not break the Goldwater Rule. I’m not sure how you came to that conclusion based on what it reads in the section.
It lists specific instances where the rule and commentary on Trump intersect, as well as citing commentators that disagree with the APA about how the Goldwater Rule is applied with Trump.
I’m not defending Trump, but don’t statements like these run counter to the Goldwater Rule?
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
For what it’s worth, the reputation of the BrandonM comment on the Dropbox post is pretty overblown compared to what was actually written. The post highlighted some concerns that were legitimate in 2007. And the tone of the comments were supportive of dropbox – the poster acknowledged the feedback and offered use cases that still would lean towards Dropbox, and BrandonM responded that they made sense and wished them luck.
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
I actually didn’t get it for a second, so I do appreciate your title.
Oh hey, fellow org user!
I’m in the same boat. I don’t do calendaring that much, but agenda is what I use when I’m time blocking tasks.
My main complaint is that I can’t get it to sync to my Google calendar. I have tried org-gcal but the gpg encryption never works for me so I just gave up. I would have liked it to have easier viewing on mobile, but that’s minor enough that I don’t care. Orgzly with notifications on lets me know when its time to do something anyway.