Yak Shaving....wildly hoping this will entertain everyone :)

I am amused by all yak shaving anecdotes. Now if you'll excuse me, I have to go back to debugging this function that formats and sends the current region to an emacs-slack buffer. My co-worker has been left hanging for a couple days now. (This is a true enough story. I got sick of cutting and pasting from emacs into the native Slack client and said "hey, I could use emacs-slack." After installing that and tracking down a very unfortunate interaction with nano-modeline, it was just a few hours of configuring emacs-slack to look reasonably nice and a few minutes to write the aforementioned function. Sadly I've forgotten what it is I was meant to send.)

If there was a stronger candidate for "pass the salt award" for all time, I've never seen it

Good; now I know a term with which to describe the last 10 years of my life. Not that anyone will bother to ask.

Yak-shaving *is* life. Life is yak-shaving.

Yak Shaving is how my `emacs.d` git repo has more stars than any practical project I have.

I’m a physics PhD student in this picture and I don’t like it.

https://www.youtube.com/watch?v=AbSehcT19u0

I do this often. Very often

https://www.youtube.com/watch?v=AbSehcT19u0

Okay, so I've been trying to learn Go for the mit 6.824 course I'm trying to follow online , and I figured it would be nice to have some auto-complete support for GoLang on my emacs right? Right? So I updated to emacs28 because the lsp server for Go wouldn't work with my version. On my journey to get lsp-server and gopls to work, I was like oooh yes it would be nice to have some auto-format and auto syntax correction. My emacs kept crashing every 45 seconds so yesterday I spent all evening trying to rollback the gdb version I installed because my macos version didn't support the latest version, which btw, also had to be codesigned. It's been 4 days now and my init.el has crazy comments but at least I'm ready to do lab1. Edit: changed gbd - > gdb gbd is the global burden of disease gdb is the debugger I didn't need

AI will shave the yaks for you.

The worst is when you shave a yak just to later discover that emacs comes with this particular shaved yak.

Just remember, yak-shaving is productive. Yak-shaving gives us things like LaTeX.

> The worst is when you shave a yak just to later discover that emacs comes with this particular shaved yak. Yes, but it's [not the right color . . . ](https://bikeshed.com/)

> G I R L S C O U T B E N E F I T Huh?

How is emacs-slack? I have learned to live with their app with a combo of XKeySnail giving me basic Emacs motion keys and their own shortcuts, which took the urgency off doing it within Emacs, but if it's slick/comfortable it may bump up the priority list. There it is, taking up 250M of memory...

Thank you. I was waiting for this.

>How is emacs-slack? Surprisingly functional. It's been around a while but I'd guess that the author included pretty much all of the then current Slack API when it was developed. The obvious things like threads and images work but there are niceties like typing indicators, notifications, emoticons, and even a wysiwyg compose window optionally available. Commits haven't been made to the repo in a long while; however, the code is a really nice example of CLOS (implemented by EIEIO) and looks to be readily maintainable if there's some sort of functionality gap. The documentation is scant (although the section on how to ascertain your credentials is succinct and correct). There aren't many (if any?) default key bindings but Hydra solved that. It's terrifically ugly out of the box (at least to my tastes) but -- as expected -- completely configurable. I'm still working on tweaks but if you're interested [my configuration is on Github.](https://github.com/bunnylushington/dot-emacs/blob/main/dot-emacs.org#slack) (Warning: other people have junk drawers; I have my emacs config: it's crufty.) What I'd like now is a function that copies the last vterm command line and output directly to a slack im/channel buffer. I wrote a really hacky first pass but when there's time I'll refine that. To be honest, the native client does a surprisingly nice job on MacOS and there are features that aren't implemented (e.g., huddles, which we use a lot at work). My workflow is almost entirely in Emacs though and simply switching to a buffer to read messages (which allows for incremental search!) is appealing. It costs little to run both clients in parallel and see what shakes out.