So, I'm currently in a middle of moving all of my calendars from Google Calendar to #emacs#orgmode in an on going effort to reduce dependency on Google.
This little project has been progressing better than expected! And now I've found a final piece of a puzzle that makes the whole thing come together: Orgzly Revived [1] (mainly for its Git syncing feature) for Android.
With this combination, I've successfully moved off Google Calendar for good and without any loss in functionality.
@louis Nice! Thanks for a nice showcase of another obvious limitation of LLMs.
Hallucinating is bad enough, but to completely fabricate new explanations on non-existing stuffs really take the cake here (but not too surprising; since fundamentally there is no concept of "truth" in LLMs anyway).
This reminded me of another case where a user asked an LLM a technical question, and it give a very plausible answer; only for the user to realized later that the correct answer is the complete "reverse" of the one that the LLM gives.
This is especially hilarious because I know a couple of companies that is building their product around Mistral AI.
Can't wait for the bubble to burst
EDIT: And no, RAG won't save LLMs; people already have to downplay the hype of what RAG can do to mitigate issues with LLMs.
So I just transitioned all of my machines (2 desktops and 1 laptop) to #kde#wayland, and am happy to report that everything is working flawlessly (yes, even the games and #steam, and yes, I use #amd graphical card - an RX580).
And the reason I took so long to switch is not because that I dislike #wayland or anything (in fact, I'm 100% neutral on the whole #wayland vs #xorg fiasco), but because I have a workflow that relies heavily on various tools that only work on #xorg. All of which I finally have time to replaced with equivalent ones that works on #wayland.
And speaking of #emacs on #wayland. It works flawlessly, of course. But for the best experience, make sure your #emacs is compiled with the pgtk ("pure" #gtk) support. I had to recompiled mine, but if you on #kubuntu/#ubuntu 23.10 (or later), then the one in the repository should be good to go.
Sadly, after months of using corfu.el, I've now reverted back to using company-mode again.
The straw the broke the camel's back is the lsp-mode's lack of support for working with corfu.el (while lsp-mode can detect and auto-configure company-mode to work with itself).
And, speaking of lsp-mode, while I try my hardest to use eglot when possible, I still have to resort to using lsp-mode when working with some languages due to the fact that lsp-mode just works better with them (e.g., Ruby, Perl, etc.).
While it might be possible to configure corfu.el to work with lsp-mode, I currently don't have enough time to look into the issue right now, so it's back to the company-mode (for now, at least).
On the bright side, prescient.el works with company-mode (via the company-prescient package) so the transition is not so painful.
When you spend hours investigating an issue on a library, and creating GitHub issues with all the information you have and the only response is from someone complaining about the formatting of your example code ... 👊
... that's when I'm reminded that stepping into #CommonLisp programming is not only a great learning exercise, but also an exercise in great restraint.
@louis Well, on the bright side, at least it doesn't seem like the guy who complained about the formatting of your example code is a member of the project you opened the bug report.
So, I finally stop being lazy and upgraded Emacs on my main desktop computer to the latest and greatest version, 29.1, and during the process I ran into this little function/minor-mode:
pixel-scroll-precision-mode.
Which, after enabled, makes mouse scrolling so silky smooth, I can't go back to how it was before.
Chalked up another reason why 29.1 is a great release of Emacs.
In case you didn't know, the combination of #emacs, #elfeed [1], and #elfeed-tube [2], turns #emacs into a powerful and featureful, RSS-based interface for watching #youtube on your terms.
If you are sick and tired of #youtube not showing new videos from the channels that you follow, then give this setup a try. I'm loving it.
@louis Thanks for the benchmark. Also, at least it's good to see that the good old, reliable #hunchentoot is the fastest among the #lisp variants here.
I think I just ran into a pretty big "gotcha" with my transition to corfu.el: it doesn't seem to work with SLIME (at least, not OOTB) and all of the solutions that I've found to make them work together so far are pretty... unsatisfactory, to say the least.
As any Common Lisper can tell you, is a pretty big deal, as SLIME is pretty much the reason why Emacs is so awesome with Common Lisp.
But just as I was about to revert back to using company-mode, I stumbled across a thread that mentioned that corfu.el does work with Sly, a fork of SLIME. So, after a quick package-install later and, lo and behold, corfu.el does work OOTB with Sly!
So, I guess I'm trying out one more shiny new "modern" Emacs package then.
@louis Congratulations! Also, will it be possible for you to write an after-action-report afterwards? I'd love to read about the Common Lisp stack that you use in the end.
