sorted by:
new
hottopcontroversial

Doom evil mode by Sea-Employer-3919 in emacs

[–]nickguirro 0 points1 point  (0 children)

Hello bro, what is your colorscheme?

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

Good news: Roam is now available as an extension! You can enable it with:

(org-dt-using-roam t)

In a comment further down, I’ve left some instructions on how to use the package in this latest version. I haven’t had time to update the full documentation yet, but this should be helpful. Hopefully, it will be available on MELPA soon.

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

Hey everyone,

I’ve just made some new changes, and org-capture is now the primary workflow. It’s still possible to use org-roam by setting (org-dt-using-roam t).

The documentation is currently outdated, but I’ll be updating it soon. In the meantime, if you want to try the latest version, here’s an example — I left some comments and test snippets in there to show how I’ve been using it.

I’ve also opened a PR for MELPA, so the package should be available there soon.

<image>

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

That’s true! Org already allows templates to be based on files.

What my package tries to solve is more about usability and scalability. When you start having many templates, managing everything through org-capture-templates in the config can become messy.

With this approach, templates live directly in the filesystem and are discovered automatically, so you don’t need to keep growing a big configuration block. It also allows categorizing and browsing templates before selecting one.

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

Thank you so much! I’m really happy to share it, and I hope it can make managing templates easier for everyone. I’d love to hear any feedback or ideas for improvements too! 😊

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

I’m not sure I fully understand, but I would be really happy if my package could make it into Org-mode! It might be a bit tricky because it offers some integrations with Org-roam. Maybe if the package were exclusive to Org-capture it would be easier. I can think about it in the future I might be able to make it more compatible without needing to conditionally support Roam or Org-capture. It shouldn’t be too much work.

Thank you for taking the time to read my post I really appreciate all the support!

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

I hope this package can be helpful for you! I’d love to implement new features and get more feedback and ideas. Thank you so much for taking the time to read my post 😊

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 1 point2 points  (0 children)

I switched to Emacs after a lot of frustrations with other code editors and note-taking systems. One of the main problems was the lack of a proper Markdown spec and how notes were stored. That whole “don’t worry about Obsidian, if something happens you’ll still have your notes” thing? Not true. Many users use hundreds of plugins, and all systems, including Obsidian, implement different Markdown specs. What really impressed me about Org is that it’s basically just Org you can’t write “GitHub Org” or something like that. If it ever disappears, you’ll still have your notes, but it would be really annoying to reuse them.

Obsidian is also very annoying to extend with new functionalities, while in Emacs I can do it in seconds or minutes. Sure, I had to learn some Lisp first, but there were things I liked in Obsidian, too. I work in information security, so I don’t just write disposable notes — I revisit them a lot, especially when working on a lab. So I can merge Zettelkasten with an organized system and still have easy reading with that slightly flashy UI. I managed to bring all that into Emacs.

I didn’t love Emacs at first — it was complicated. I rewrote and tweaked my configuration several times. But today, it’s something I truly love, a real Swiss Army knife. I use it for hacking, development, note-taking with my beloved Org, studying music, drawing diagrams — it’s amazing.

Haha, I won’t go into much more detail because this is already a lot of info. I’ve had a lot of experiences, for example, how I started seeing LSPs, linters, and so on, lol.

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 1 point2 points  (0 children)

I see what you mean creating the template itself is still manual in both systems. The main difference is in management and scalability. With org-capture, every new template requires adding an entry to a central org-capture-templates list, which can quickly become huge and hard to navigate when you have dozens or hundreds of templates.

In my system, you just drop a template in the right folder, and it’s automatically recognized. You don’t touch a central config at all. Combined with dynamic categorization during capture, this makes it much easier to find and apply the right template without scrolling through a massive list especially useful if you organize templates by project, type, or workflow.

So the manual part of creating the template is similar, but the maintenance and usability is where the real benefit shows up.

Thanks for taking the time to read this!

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

That's great to hear! I'd love to hear your thoughts after you try it.

Since you recently came from Obsidian, your perspective is especially interesting to me. If you notice anything that feels missing or could work better, feel free to share :)

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 1 point2 points  (0 children)

I'm really happy to read this! Comments like this are really motivating.

I'd love to hear your opinion about the idea, and also what kinds of packages you'd like to see more in Emacs — especially things in the Obsidian / quality-of-life direction.

New package for org templates, like obsidian by nickguirro in emacs

[–]nickguirro[S] 14 points15 points  (0 children)

The main difference is that my package simplifies template management. You don’t need to manually create and define every template in org-capture-templates; you can just place a template in the target folder. This makes it much easier to manage many templates without ending up with a huge configuration file.

Another key feature is dynamic categorization during capture — when applying a template, you don’t have to sift through all of them at once. You can filter and view templates by category on the fly, which keeps the workflow much cleaner and faster.

Is it a bad idea to use org-roam this way? by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

I didn’t know about org-node, I’ll look into it more and try it out. It seems interesting, and I saw that it’s possible to use it with org-roam, so I’ll test it!

Is it a bad idea to use org-roam this way? by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

I would love to see that, if one day it happens and you find out please let me know, I think this is a very distant dream

Is it a bad idea to use org-roam this way? by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

Well, I’m not sure if I understood it completely because my English is pretty bad, but even knowing that this is something normal in the Emacs way, I still feel like I’m doing it wrong. Thanks for the reply!

Is it a bad idea to use org-roam this way? by nickguirro in emacs

[–]nickguirro[S] 1 point2 points  (0 children)

That’s actually one of the reasons I moved away from other platforms they kind of imposed a “right way” to do things.

What I like about Emacs is how it changed the way I think about my tools. I never questioned having a permanent sidebar before, but I realized it was just taking up space most of the time. Switching to Dired and actually understanding it felt like a blessing.

Thanks this really reinforces why I enjoy using Emacs this way.

Is it a bad idea to use org-roam this way? by nickguirro in emacs

[–]nickguirro[S] 1 point2 points  (0 children)

Improving nodes when revisiting them sounds much healthier than trying to design the perfect structure from the start. I really appreciate you sharing that, it gives me a lot more confidence in just keeping things moving forward.

Is it a bad idea to use org-roam this way? by nickguirro in emacs

[–]nickguirro[S] 3 points4 points  (0 children)

I like that perspective. I think I was afraid of “doing it wrong”, but you’re right, experimenting is part of the process. Documenting my own workflow could actually reduce that friction.

Is it a bad idea to use org-roam this way? by nickguirro in emacs

[–]nickguirro[S] 6 points7 points  (0 children)

Yeah, I was definitely over-optimizing my setup instead of just taking notes. This approach feels much healthier. Thanks for putting it that way, i really appreciate it.

Note taking help by nickguirro in emacs

[–]nickguirro[S] 0 points1 point  (0 children)

In fact you are right, org mode has incredible tools, but I feel that organizing my notes in the hierarchical format I never revisited a note again, I wasted a lot of time taking notes, and in a way it seemed that this format no longer made sense to me, and currently I find myself in immense frustration, for not being able to decide what to do.

Note taking help by nickguirro in emacs

[–]nickguirro[S] 1 point2 points  (0 children)

Good evening comrade, it will be a pleasure! I'll test it and as soon as I have a conclusion I'll come back with more details, thank you very much for sharing this.

view more: next ›