flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.3K
active users

#doomemacs

1 post1 participant0 posts today

Dum kelka monati me uzis #doomemacs, ma pokope me ne volis uzar ol plu. Nun mi volas uzar emacs sole, tale me povas lernar komo uzar ol bone.

On povas dicar ke DoomEmacs es same kam Nvim e me ja savas komo uzar Nvim bone, ma til nu uzante DoomEmacs me remarkas ke me ne savas komo uzar #emacs nek la maxim baza kozi.

#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)

Alright, I'm actually curious as apparently some people are saying not use the terminal to access #Emacs. Though I prefer it myself, seems intuitive for my workflow. Though, I'm not sure if it is because I'm using #DoomEmacs over the vanilla GNU Emacs. What do you say ? Do you use your terminal for Emacs, or do you use the GUI ? Do you use Doom Emacs, GNU Emacs, or another spin of Emacs ?

Poll in comments

Anyone on here a #doomemacs user that would be willing to help me figure out why my Rust LSP integration isn't working? The rust-analyzer seems to be running, and I'm not seeing any errors in my LSP buffer or anything, but I am not getting anything but syntax highlighting. Really hoping to make this emacs thing work! #emacs

#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. 😩

#Golang development in #Emacs (#DoomEmacs to be precise) is surprisingly nice. I missed having usable refactoring tools. "Extract to function" is something every language should have, having to write the entire function header with every type by hand is such a waste of time. At least "rename symbol" tends to work in every LSP implementation.

Replied in thread

@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!