I noticed a "kagi" link type in the list when I went to create a link in #OrgMode

I love @kagihq but I never added any Kagi specific support.

Asked Claude to tell me where it came from and what it was for.

Turns out, it is for the search engine, and it's baked into org-mode / #emacs (or maybe a #DoomEmacs add-on?)

That's pretty cool.

For my #writing i thought that #doomemacs was the right choice, because i thought it will be more easy for a non programmer like me. It was not. I was trying things that i've never understood and it became frustrating.

The best decision i've made was to restart with GNU #emacs following some tutorials. Now i have a simple config that works. And i've learned ... a lot.

I just love emacs

Should I start out with vanilla #emacs , #doomemacs, #spacemacs or some other flavor? More importantly: why.

Notes: 40% Colemak layout user. Coming from VSCodeium as main editor. I would want to go full Emacs eventually.

There is a lot going for #Obsidian in terms of UI performance and UX niceties, but one thing keeps pulling me back to #DoomEmacs and #OrgRoam: laser focused keyboard oriented setup out of the box

I can move subtrees around quicker than I can think.

(or I could if #Emacs didn't freeze up for 30 seconds randomly. oh well, can't have it all. any by "it all" i mean "widespread adoption of async UI patterns in your favorite editor".)

I have really been wrestling lately with my config.el file for @doomemacs

The issue seems to be that the after! macro does *not* work, and I end up with custom configurations not loading

This manifests with is my dape-configs, so when I relaunch emacs after an update (I use emacsclient) I get... no configs (until I go to config.el and C-x C-e on those blocks)

I think my hacky solution has been to just use use-package dape instead, but how is after! supposed to work?

#emacs #doomemacs

I'm considering apostatizing from the church of #emacs. the original allure was, for everything you want to do... "emacs has a package for that." that largely seems to hold up.
but.

#doomemacs manages the whole dependency graph for me, which is pretty great. Except when it fails. I made an attempt to learn #cobol for job hunting reasons, so i had to leave emacs to set that up.
projectile seems to have some weird rules by which it decides what is and is not a project.
but there's also the other old cliche; "emacs is a fine operating system; it just doesn't have a good text editor." doom emacs lets you use the spacebar instead of ctrl for everything, and on top of that includes evil mode so you use vim motions... Emacs wants to be a text editor; as evidenced by the fact that one never opens a "project", one opens text files. So if all of these other things are extra tools, why not just use vim? the text editor you're mimicking anyway?

on the other hand, all of these are skill issues. 🤷