Hmm… How bad idea is to start using Doom Emacs?
Hmm… How bad idea is to start using Doom Emacs?
I've been using #Emacs for the last couple of months now for all my daily work (I'm a translator, not a programmer) and here's a thought.
Of course, I stumbled upon rather contrasting recommendations:
1) Don't use vanilla, use #DoomEmacs or #Spacemacs. Preferably Doom. Well, I tried this in the past, but it didn't stick. It''s everything and the kitchen sink, but you generally don't know if you really need all this. So you study Doom, not Emacs. I might get back to it in the future. I did prefer Spacemacs, though (aesthetically).
2) Use vanilla and spend ten years building your own config. This sounds fairly reasonable, because you naturally learn the program itself, not its plugins. But it's a huge timesink when you start to "build your own Emacs". So you'd end up with DoomEmacs, but badly written, slow and constantly breaking on every update.
I went with the second alternative and here's what I got for my personal usecase:
me@desktop:~$ grep "use-package" .emacs.d/init.el | wc -l
8
Eight packages. howm, inkpot-theme, which-key, avy, counsel, general, annotate, markdown-mode. I didn't even bother to make annotate work for now, so it's 7. And I don't really use avy, so it could be 6.
That's all I need for now. For several months I haven't had a moment yet when I thought that I need something else or that my workflow is getting somewhat cumbersome.
Of course, this doesn't mean that my setup is perfect. But my point is: configuring your own Emacs could be way easier than you might think (depending on the workflow), and you probably don't need to fight a bazillion packages waging civil war in your config file.
Unleashing the Power of Doom Emacs: A Modern Configuration Framework
Doom Emacs is revolutionizing the way developers interact with Emacs by providing a fast, efficient, and customizable configuration framework. Designed for those who seek a blend of performance and si...
https://news.lavx.hu/article/unleashing-the-power-of-doom-emacs-a-modern-configuration-framework
#DoomEmacs / #Emacs users
dafuck is this trying to tell me? I'm in an #OrgMode document and it keeps showing me these square brackets in the status bar at the bottom. It's only in THIS document though.
I thought maybe I had some broken link tags or something but there are zero square brackets in this document. (confirmed with grep and ripgrep)
So went through a few complicated setups now that I have time.
#neomutt was ok but clunky to use.
Set up mbsync and msmtp with #nix, and they seem to be working fine.
Had Mu4e working in #doomemacs , I like the defaults in doom, but when it comes to customizing it like valina #emacs, it seems to fall short.
Now I'm trying to get mu4e set up in my vanilla emacs config. We'll see how it goes, and if I get sent to spam again.
For the first part of #DecemberAdventure I almost figured out how to publish my #OrgMode / #OrgRoam pages. Originally I wanted to work on and write about #65cha02 but Org's publishing config is, uh, a bit arcane. I also ran into the bug where if you use a URI scheme that Org doesn't know about it gives you an error. Already reported that bug years ago when I used it to write my CV and wanted a tel link in it, looks like it's still unfixed.
Well, at least I'm learning more about #Emacs... the hard way. Still, using #DoomEmacs is actually really nice, I'm finally getting into #Magit and it's the best way to selectively stage changes in #git that I've encountered so far.
Also, if anyone knows how to export only pages that have a given tag, I'd love to hear it. No, select_tags is not what I want. I want everything in my memex to be private by default.
Edit: Okay, couldn't leave it at that. Powered my way through even more computer weirdness and now I have a glorious website to document my journey. Woohoo!
https://raingloom.srht.site/20241201222215-december_adventure.html
Edit2: Now also available on this domain name I've been meaning to use:
https://brain.trainpats.eu/
Practicando #html #css #javascript realicé dos proyectos. Una página de información médica y un calculador de gasto eléctrico.....
https://zylognoise.github.io/gastoelectrico/
https://zylognoise.github.io/preparacion/
Pequeñas cosas que me costaron en general. Sobretodo la parte estética en css ... ufff
Todo realizado en #doomemacs #linux #opensuse #gnome ..
#Emacs (or more specifically: #DoomEmacs) people:
If I have the following lines in a buffer, is there a way I can I quickly show a character-wise diff between them? (Preferably by visually selecting them and running a command.)
```
expected: "1729586933081/-O9nPXnrHyu_6JftQXGQ"
actual : "1729586933081/-O9nPXnrHyu_6JftQXGP"
```
I just wasted way too much time saying “it’s the same picture”, when it's not.
Cómo empezar con Emacs: Distribuciones
La experiencia inicial para quienes prueban Emacs por primera vez puede ser un poco intimidante. Una posible alternativa para facilitar el proceso: distribuciones.
https://picandocodigo.net/2020/como-empezar-con-emacs-distribuciones/
Why does the Greek font become bigger when a phonetic mark is added?
My setup is Doom v3.0.0 pre and emacs 29.1 with Doom default font.
@danderzei Hi, I finished reading the book yesterday and here is my short review.
First, thanks again, your book arrived at the perfect moment for me, as I was starting think about migrating from #Obsidian to #Emacs. This book was a real help to get me started. As you said in chapter 9, #EWS is a great way to save some time and have tools needed to be able to work immediately after learning the basics of Emacs.
Not everyone has the time and energy to learn as well as to start tinkering with a new software, since these can be necessary when starting from a vanilla configuration. I love to play with tools but I'm not sure if I would have been able to make the transition to Emacs without the foundation you created with EWS. For example, you implemented many quality of life improvement to make sure every part of the writing process are made as easy as possible, something that can be hard to produce for a new user who is not sure of the workflow to implement. For example, when I entertained the idea of moving to Emacs, I was not sure if #Denote or #Org-Roam was the best option for me, but I can see now that choosing between either was just a small step, and that the configuration you offer with EWS is very well crafted and functional.
I appreciate the fact that you stayed as close as possible to the default Emacs experience. This way, a new user can start writing with the different tools you offered right for the start while having the space to eventually add new packages and play with the configuration. I remember playing with #Spacemacs years ago and it was overwhelming to make modifications to this distribution, even though the documentation was good.
Your book makes learning Emacs pleasant, since it is not written in a dry way as your usual manual. Playing with the software at the same time is the best way to read your book and I now feel confident using it for my own projects. External resources like Prot's channel and @daviwil Systemcrafters.net were really complimentary to reading your book, but I don't see this as a negative point. Maybe pointing to more online resources could be a good idea for the newcomers.
I must say, I know how to search info online and I like to deep into things, so I don't know if I'm the best candidate to review this book as I think you wanted to offer a distribution for someone entirely new to Emacs, but still, I thank you a lot for this rich book. I've already started changing some configurations and I don't feel the need at all to switch to something with #Doomemacs (even though I will definitely try to implement Evil mode in EWS).
A final word to say I also appreciated the integration of well known tools in EWS. In addition to being a good platform for writing, it integrates other ideas like #GTD and it's possible to come with some knowledge of #Zettelkasten, #PKM or Second brain systems and methodology and have them work out of the box. It could be a good idea to point it out in the introduction so people familiar with those will be even more motivated to learn about EWS and read until then end.
Thanks again for this project! I hope I will be able to contribute in some ways in the future to some of those projects that were leveraged to make EWS possible, or maybe to EWS by itself. I look forward diving deeper into it!
Morning all...
As promised, new #XeroLinux toolkit update bringing you #emacs with @distrotube custom config.. Maybe #DoomEmacs soon. No promisses on that though.. #FOSS #Linux #OpenSource
After switching to Emacs full time a month ago, I’m in the uncomfortable and weird phase where I feel productive while coding in Emacs but still craving for a mouse click or two, and if I switch to an IDE I instantly crave my evil mode shortcuts and all the contextual tools Emacs offers.
Let’s see what happens in a month from now.
@mechatour for being productive and somewhat comfortable fast I went with #DoomEmacs which is a ready-made config catered to people that are used to many out-of-the-box features for editors/IDEs
it took me a few months, but I managed to make emacs feel like my primary editor (which was hard after being comfortable with vs code)
shouldn't be long until i start writing my own elisp now :)
I keep tampering with my sprawling, custom #Emacs config, because I'm never quite satisfied. Should I try #DoomEmacs or #SpaceEmacs in 2024? (Or am I just rubbing against dukkha, the Other´s juissance, capitalism or some other existential constant)?
Yesterday I ran #Ollama with #Llama2 from #emacs using https://github.com/karthink/gptel . I was able to get it going from nothing to fully working in about 10 mins.
Spent the weekend reviewing articles and videos from @daviwil and decided I'm going to try Doom Emacs. Got the basic set up working before end of work, tomorrow I'll have a proper go. Just one thing... How do I turn off evil key bindings?
#emacs
#doomEmacs
#evilMode
When is the right time to declare #emacs bankruptcy?
It's eight years old
.. and has pivoted from #spacemacs to #doomemacs.
.. and "supports" Manjaro, Manjaro with Guix, Guix System, Windows, WSL, WSL
with Guix System
.. and many different hardware configurations
.. and six different "contexts" (e.g. clients)
.. and many different forms of note-taking, zettlekasten, gtd etc.
Just spent a day wrestling the notes into submission, and not looking forward to taming my ~7000 line configuration.