#doomemacs — Public Fediverse posts

Went back from #doomemacs to my own #emacs configuration. There were just too many unknowns, too little documentation - basically too much magic.

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

@tylerayoung @katafrakt I am really looking forward to the #Neovim and #DoomEmacs integration \o/

I think #DoomEmacs has thoroughly undone my #Plan9 conditioning.
Or maybe no longer using a #ThinkPad is the actual reason. All the touchpads I use are worse than the Clit Mouse TM. They are still better than having to reach for an actual mouse, but damn, I miss that red dot.

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. 🤷

Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. https://lap.dev/floem/ :moomin_yay:
The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. https://lap.dev/floem/ :moomin_yay:
The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. https://lap.dev/floem/ :moomin_yay:
The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. https://lap.dev/floem/ :moomin_yay:
The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. https://lap.dev/floem/ :moomin_yay:
The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

I've been a #DoomEmacs user for some time, now, even having curated my own literate config out of their "static" files - along with all the extra stuff one adds to such a thing.

As one does, in the past I've also attempted to do my own #emacs config from scratch, usually falling into the "let's recreate doom!" hole, whether I wanted to or not (thus the reason I just went the route I did).

Over the past couple of months I've decided to - slowly - do the emacs bankruptcy declaration. Now, just to make things even more interesting I have decided against the use-package macro. Why? Because why not!

I've been using my scratch build for a month or so, haven't even opened my doom config up. It's been a great process, learning process, more understand of the process. It helps that I've been on a learn lisp quest for the past couple of years, too (#CommonLisp, #sbcl, #clojure, #elisp of course).

The large emacs distros are great an an excellent way to find curated packages. Doom is even a really nice framework. Sometimes you just want to do your own thing.

I've been a #DoomEmacs user for some time, now, even having curated my own literate config out of their "static" files - along with all the extra stuff one adds to such a thing.

As one does, in the past I've also attempted to do my own #emacs config from scratch, usually falling into the "let's recreate doom!" hole, whether I wanted to or not (thus the reason I just went the route I did).

Over the past couple of months I've decided to - slowly - do the emacs bankruptcy declaration. Now, just to make things even more interesting I have decided against the use-package macro. Why? Because why not!

I've been using my scratch build for a month or so, haven't even opened my doom config up. It's been a great process, learning process, more understand of the process. It helps that I've been on a learn lisp quest for the past couple of years, too (#CommonLisp, #sbcl, #clojure, #elisp of course).

The large emacs distros are great an an excellent way to find curated packages. Doom is even a really nice framework. Sometimes you just want to do your own thing.

I've been a #DoomEmacs user for some time, now, even having curated my own literate config out of their "static" files - along with all the extra stuff one adds to such a thing.

As one does, in the past I've also attempted to do my own #emacs config from scratch, usually falling into the "let's recreate doom!" hole, whether I wanted to or not (thus the reason I just went the route I did).

Over the past couple of months I've decided to - slowly - do the emacs bankruptcy declaration. Now, just to make things even more interesting I have decided against the use-package macro. Why? Because why not!

I've been using my scratch build for a month or so, haven't even opened my doom config up. It's been a great process, learning process, more understand of the process. It helps that I've been on a learn lisp quest for the past couple of years, too (#CommonLisp, #sbcl, #clojure, #elisp of course).

The large emacs distros are great an an excellent way to find curated packages. Doom is even a really nice framework. Sometimes you just want to do your own thing.

I've been a #DoomEmacs user for some time, now, even having curated my own literate config out of their "static" files - along with all the extra stuff one adds to such a thing.

As one does, in the past I've also attempted to do my own #emacs config from scratch, usually falling into the "let's recreate doom!" hole, whether I wanted to or not (thus the reason I just went the route I did).

Over the past couple of months I've decided to - slowly - do the emacs bankruptcy declaration. Now, just to make things even more interesting I have decided against the use-package macro. Why? Because why not!

I've been using my scratch build for a month or so, haven't even opened my doom config up. It's been a great process, learning process, more understand of the process. It helps that I've been on a learn lisp quest for the past couple of years, too (#CommonLisp, #sbcl, #clojure, #elisp of course).

The large emacs distros are great an an excellent way to find curated packages. Doom is even a really nice framework. Sometimes you just want to do your own thing.

I've been a #DoomEmacs user for some time, now, even having curated my own literate config out of their "static" files - along with all the extra stuff one adds to such a thing.

As one does, in the past I've also attempted to do my own #emacs config from scratch, usually falling into the "let's recreate doom!" hole, whether I wanted to or not (thus the reason I just went the route I did).

Over the past couple of months I've decided to - slowly - do the emacs bankruptcy declaration. Now, just to make things even more interesting I have decided against the use-package macro. Why? Because why not!

I've been using my scratch build for a month or so, haven't even opened my doom config up. It's been a great process, learning process, more understand of the process. It helps that I've been on a learn lisp quest for the past couple of years, too (#CommonLisp, #sbcl, #clojure, #elisp of course).

The large emacs distros are great an an excellent way to find curated packages. Doom is even a really nice framework. Sometimes you just want to do your own thing.

Sometimes doom upgrade claims "Doom is already up-to-date!" for days when it's clearly not the case. A quick fix which works for me is:

[in ~/.config/emacs]
```
git pull origin master
```

Followed by:

```
doom sync -u
```

#emac #doomemacs

I am about to give a workshop about #reproducibility in the context of #ROOT #technology using #doomemacs #emacs (cf. https://doi.org/10.5281/zenodo.17157587).

Now I am wondering how I can make sure that the participants have installed all necessary programmes? I came up with a little test script: Please #help me to improve the script testing for edge-cases; execute the script and let me know if it works and/or what can I improve: https://gitlab.git.nrw/-/snippets/113

Thank you! #retoot #BoostoK

I've been doing a "just for the giggles" exercise over the last couple of weeks. Attempting to make an #emacs config "of my own" (yeah, that's hilarious) that doesn't utilize "use-package". I dunno why, besides just wanting to get a delete knowledge of the interior workings.

I've been a #DoomEmacs user for a really long time now and have a total literate config built out around it (including the static files they provide). I like it as a framework, but there are just some things that I might like to try and swap out, which would be easier with an "own" setup.

I just didn't know if I'm actually gonna finish this route. 🤷‍♂️

#Fedora does not support #doomemacs
#Cosmic does neither support middle mouse paste nor japanese/anthy input
#Sway ignores input switch configuration completely

#iwlwifi broke after a recent NixOS upgrade (firmware/kernel issue, not really distro-specific), but being forced #offline finally got me to work on my #OrgRoam memex. :neofox_uwu:
Linked a bunch of lonely nodes together.
Once I got the network back online I even wrote some #Elisp to replace old link that point to files with UUID ones.
And yeah, I needed a search engine for that, because the built-in docs for #Emacs - while often handy - are lacking in examples and assume a bit too much up-front knowledge. I'm still not sure what the heck org-element-context returns and why I should need a special function to index it. Say what you will about the complexity of #JavaScript or #Python, having built-in data types for lists, sets, and maps makes it a lot easier to poke at data.
But at least I could hack together about half of it from offline sources.

One issue that surprised me is that default setup for editing ELisp in #DoomEmacs is still not entirely user friendly. Lots of things work out of the box, which is really cool, but some simple things like automatic indentation are not really consistent.
When I saved the file, it got reformatted in a way that broke its structure.
When I tried to de-indent a line, it deleted too much whitespace, instead of just going back a single level, so I had to use C-x TAB, which is unnecessarily many keystrokes for such a common operation.

All in all, I'm impressed at how productive I can be with it and I hope that the jankiness will be less of an issue once I've gained some Elisp experience.

#iwlwifi broke after a recent NixOS upgrade (firmware/kernel issue, not really distro-specific), but being forced #offline finally got me to work on my #OrgRoam memex. :neofox_uwu:
Linked a bunch of lonely nodes together.
Once I got the network back online I even wrote some #Elisp to replace old link that point to files with UUID ones.
And yeah, I needed a search engine for that, because the built-in docs for #Emacs - while often handy - are lacking in examples and assume a bit too much up-front knowledge. I'm still not sure what the heck org-element-context returns and why I should need a special function to index it. Say what you will about the complexity of #JavaScript or #Python, having built-in data types for lists, sets, and maps makes it a lot easier to poke at data.
But at least I could hack together about half of it from offline sources.

One issue that surprised me is that default setup for editing ELisp in #DoomEmacs is still not entirely user friendly. Lots of things work out of the box, which is really cool, but some simple things like automatic indentation are not really consistent.
When I saved the file, it got reformatted in a way that broke its structure.
When I tried to de-indent a line, it deleted too much whitespace, instead of just going back a single level, so I had to use C-x TAB, which is unnecessarily many keystrokes for such a common operation.

All in all, I'm impressed at how productive I can be with it and I hope that the jankiness will be less of an issue once I've gained some Elisp experience.

#iwlwifi broke after a recent NixOS upgrade (firmware/kernel issue, not really distro-specific), but being forced #offline finally got me to work on my #OrgRoam memex. :neofox_uwu:
Linked a bunch of lonely nodes together.
Once I got the network back online I even wrote some #Elisp to replace old link that point to files with UUID ones.
And yeah, I needed a search engine for that, because the built-in docs for #Emacs - while often handy - are lacking in examples and assume a bit too much up-front knowledge. I'm still not sure what the heck org-element-context returns and why I should need a special function to index it. Say what you will about the complexity of #JavaScript or #Python, having built-in data types for lists, sets, and maps makes it a lot easier to poke at data.
But at least I could hack together about half of it from offline sources.

One issue that surprised me is that default setup for editing ELisp in #DoomEmacs is still not entirely user friendly. Lots of things work out of the box, which is really cool, but some simple things like automatic indentation are not really consistent.
When I saved the file, it got reformatted in a way that broke its structure.
When I tried to de-indent a line, it deleted too much whitespace, instead of just going back a single level, so I had to use C-x TAB, which is unnecessarily many keystrokes for such a common operation.

All in all, I'm impressed at how productive I can be with it and I hope that the jankiness will be less of an issue once I've gained some Elisp experience.

#iwlwifi broke after a recent NixOS upgrade (firmware/kernel issue, not really distro-specific), but being forced #offline finally got me to work on my #OrgRoam memex. :neofox_uwu:
Linked a bunch of lonely nodes together.
Once I got the network back online I even wrote some #Elisp to replace old link that point to files with UUID ones.
And yeah, I needed a search engine for that, because the built-in docs for #Emacs - while often handy - are lacking in examples and assume a bit too much up-front knowledge. I'm still not sure what the heck org-element-context returns and why I should need a special function to index it. Say what you will about the complexity of #JavaScript or #Python, having built-in data types for lists, sets, and maps makes it a lot easier to poke at data.
But at least I could hack together about half of it from offline sources.

One issue that surprised me is that default setup for editing ELisp in #DoomEmacs is still not entirely user friendly. Lots of things work out of the box, which is really cool, but some simple things like automatic indentation are not really consistent.
When I saved the file, it got reformatted in a way that broke its structure.
When I tried to de-indent a line, it deleted too much whitespace, instead of just going back a single level, so I had to use C-x TAB, which is unnecessarily many keystrokes for such a common operation.

All in all, I'm impressed at how productive I can be with it and I hope that the jankiness will be less of an issue once I've gained some Elisp experience.

#iwlwifi broke after a recent NixOS upgrade (firmware/kernel issue, not really distro-specific), but being forced #offline finally got me to work on my #OrgRoam memex. :neofox_uwu:
Linked a bunch of lonely nodes together.
Once I got the network back online I even wrote some #Elisp to replace old link that point to files with UUID ones.
And yeah, I needed a search engine for that, because the built-in docs for #Emacs - while often handy - are lacking in examples and assume a bit too much up-front knowledge. I'm still not sure what the heck org-element-context returns and why I should need a special function to index it. Say what you will about the complexity of #JavaScript or #Python, having built-in data types for lists, sets, and maps makes it a lot easier to poke at data.
But at least I could hack together about half of it from offline sources.

One issue that surprised me is that default setup for editing ELisp in #DoomEmacs is still not entirely user friendly. Lots of things work out of the box, which is really cool, but some simple things like automatic indentation are not really consistent.
When I saved the file, it got reformatted in a way that broke its structure.
When I tried to de-indent a line, it deleted too much whitespace, instead of just going back a single level, so I had to use C-x TAB, which is unnecessarily many keystrokes for such a common operation.

All in all, I'm impressed at how productive I can be with it and I hope that the jankiness will be less of an issue once I've gained some Elisp experience.

Okay. It's finally time to try something new. So, I'm switching to #DoomEmacs as my main (and only) text editor. I'm curious to see how it will be and how long it will take me to get used to it. :)

And a question for the community here—what do you use for #orgmode on iPhone? I've seen that there are several different apps, but I can't really decide which one to choose. I want it primarily for notes and working with them.

@felix If everything was supported and pre-installed, people would complain emacs is bloated and would still look for a configuration framework. If you know emacs you don’t need a configuration framework; you configure emacs to your specific needs. Otherwise #doomemacs has you covered. Using it for tasks other than programming I appreciate it can be molded to my needs and look like a text editor and not an ide. And btw I think it’s astonishingly modern considering for example how smoothly and elegantly ai tools were integrated without requiring a paradigm change or redesign of the ui of workflows.

#siem —Map all your data models from sourcetype. Using #org files for all documentation. #knowyourdata. #emacs #doomemacs.

Frustrated with how #spacemacs has kept kicking me in the shins with packages after upgrades (either of #emacs or spacemacs itself).

Giving a try to #DoomEmacs now.

Let's see how that puppy works.

Hmm , didn’t document and forgot how I setup guix shell to use #doomemacs

‘’’
guix shell emacs guile guile-goblins emacs-geiser-guile emacs-geiser — emacs
‘’’

🎉 Congratulations, tech wizards! You've finally managed to cram yet another ancient programming language into Doom Emacs. #Ada #coding with syntax highlighting, #LSP, and Alire support—because nothing screams “cutting-edge” like 1980s technology. 🚀 And remember, every line of Ada written is a small victory for #nostalgia over practicality! 🤖
https://github.com/tomekw/doom-ada #techwizards #DoomEmacs #HackerNews #ngated

🎉 Congratulations, tech wizards! You've finally managed to cram yet another ancient programming language into Doom Emacs. #Ada #coding with syntax highlighting, #LSP, and Alire support—because nothing screams “cutting-edge” like 1980s technology. 🚀 And remember, every line of Ada written is a small victory for #nostalgia over practicality! 🤖
https://github.com/tomekw/doom-ada #techwizards #DoomEmacs #HackerNews #ngated

🎉 Congratulations, tech wizards! You've finally managed to cram yet another ancient programming language into Doom Emacs. #Ada #coding with syntax highlighting, #LSP, and Alire support—because nothing screams “cutting-edge” like 1980s technology. 🚀 And remember, every line of Ada written is a small victory for #nostalgia over practicality! 🤖
https://github.com/tomekw/doom-ada #techwizards #DoomEmacs #HackerNews #ngated

🎉 Congratulations, tech wizards! You've finally managed to cram yet another ancient programming language into Doom Emacs. #Ada #coding with syntax highlighting, #LSP, and Alire support—because nothing screams “cutting-edge” like 1980s technology. 🚀 And remember, every line of Ada written is a small victory for #nostalgia over practicality! 🤖
https://github.com/tomekw/doom-ada #techwizards #DoomEmacs #HackerNews #ngated

Doom-ada: Doom Emacs Ada language module with syntax, LSP and Alire support

https://github.com/tomekw/doom-ada

#HackerNews #DoomEmacs #AdaSyntax #LSP #Alire #Support #ProgrammingLanguages

Doom-ada: Doom Emacs Ada language module with syntax, LSP and Alire support

https://github.com/tomekw/doom-ada

#HackerNews #DoomEmacs #AdaSyntax #LSP #Alire #Support #ProgrammingLanguages

Doom-ada: Doom Emacs Ada language module with syntax, LSP and Alire support

https://github.com/tomekw/doom-ada

#HackerNews #DoomEmacs #AdaSyntax #LSP #Alire #Support #ProgrammingLanguages

Doom-ada: Doom Emacs Ada language module with syntax, LSP and Alire support

https://github.com/tomekw/doom-ada

#HackerNews #DoomEmacs #AdaSyntax #LSP #Alire #Support #ProgrammingLanguages

Doom-ada: Doom Emacs Ada language module with syntax, LSP and Alire support

https://github.com/tomekw/doom-ada

#HackerNews #DoomEmacs #AdaSyntax #LSP #Alire #Support #ProgrammingLanguages

I tried to stop using channels, as some blog post suggested. It didn't work, so I ended up adding them back and updating the "normal" way.

There were also the typical package renaming cases, like:
* pulseaudio was moved to service,
* kate top level package was moved to kdePackages,
* nerdfonts were split into many individual font packages:
* Just deleted since I don't use #DoomEmacs

2/2

joining the church of #emacs (via #doomemacs )...

#magit just isn't as good as #sublimemerge. I can't deny it. which means, I intend to go forward using tools *outside* of emacs, and will never *truly* join the cult.
but that's fine. emacs insists it's a text editor as opposed to an IDE.
...i just don't get to eat lunch at the cool kids' table.

I started migrating to a new company laptop. As expected, moving all dev setup was a breeze thanks to #NixOS.

Setting up my mouse was a pain. For whatever reason, #Logitech G HUB detected my mouse inactive until I allowed it in Screen & System Audio Recording. I also needed to re-set my macros (screen left/right).

Next one was #spacemacs. I decided to try #doomemacs, and was fighting a lot installing emacs in a proper way on MacOS. What eventually worked was this:
```
brew tap d12frosted/emacs-plus
brew install emacs-plus
ln -s /usr/local/opt/emacs-plus/Emacs.app /Applications/Emacs.app
```

After having my failed Doom installation in ~/.config/doom.

EDIT: just did this again, and I had to use ~/.emacs.d, which is mentioned in doomemacs' Getting Started section, but not in the main README.

Then, doom install, doom sync, and it should work.

Setup org-cal-dav - those 'events' there? synced to everywhere else I check my calendar. I'd been putting this off as something that I thought was going to be complicated and potentially mess up my org files - working very nicely and no issues so far.

#orgmode #emacs #doomemacs #calendar #orgagenda

Oh shit... #LSP just works in #DoomEmacs under TRAMP? So... why did I waste hours trying to get lsp-proxy to work? :neofox_facepalm:

Edit: #Projectile on the other hand does *not* work, or at least not as well as it should.

People of Emacs and Org Mode:
Are there any packages to manage a project? I have projectile, but that's more for coding. I mean like a house move or fence build kinda project: something that has multiple todos and will take a protracted amount of time.

Failing any specific package for that, what about a org template for said project?

TYIA

#emacs #org #orgMode #GNUEmacs #doomemacs #spacemacs #ProjectPlanning #GTD

People of Emacs and Org Mode:
Are there any packages to manage a project? I have projectile, but that's more for coding. I mean like a house move or fence build kinda project: something that has multiple todos and will take a protracted amount of time.

Failing any specific package for that, what about a org template for said project?

TYIA

#emacs #org #orgMode #GNUEmacs #doomemacs #spacemacs #ProjectPlanning #GTD

People of Emacs and Org Mode:
Are there any packages to manage a project? I have projectile, but that's more for coding. I mean like a house move or fence build kinda project: something that has multiple todos and will take a protracted amount of time.

Failing any specific package for that, what about a org template for said project?

TYIA

#emacs #org #orgMode #GNUEmacs #doomemacs #spacemacs #ProjectPlanning #GTD

People of Emacs and Org Mode:
Are there any packages to manage a project? I have projectile, but that's more for coding. I mean like a house move or fence build kinda project: something that has multiple todos and will take a protracted amount of time.

Failing any specific package for that, what about a org template for said project?

TYIA

#emacs #org #orgMode #GNUEmacs #doomemacs #spacemacs #ProjectPlanning #GTD

People of Emacs and Org Mode:
Are there any packages to manage a project? I have projectile, but that's more for coding. I mean like a house move or fence build kinda project: something that has multiple todos and will take a protracted amount of time.

Failing any specific package for that, what about a org template for said project?

TYIA

#emacs #org #orgMode #GNUEmacs #doomemacs #spacemacs #ProjectPlanning #GTD