I wanted to share in this article the fruit of almost a year of trial and error to shape a configuration that made my Doom Emacs a fully featured Swift/iOS development environment.
Xcode is still far ahead (previews, instruments as examples), but still; that config gave me the opportunity to stay in Doom Emacs for 98% of the time.
by sukuva
1 subcomments
As someone that has no know how of iOS app development, this post is well written and concise. As a regular doom emacs user, I often try to make the best out of it whenever I can. I don't use LSPs at all but I am curious, do you use the same LSPs as Xcode in this case?
by sparsethots
2 subcomments
It’s interesting how easy it is to tell ai was used to write this despite it having none of the obvious mannerisms. I wonder what I would have thought of this article before 2022, or if I just don’t like this style because of overexposure or something
by whois
1 subcomments
Nice article. How has lsp mode been with Emacs? I've been continuously battling slow downs and hangs using lsp mode w Python and have tried many approaches like lsp-bridge which tries to do the majority of the work outside of emacs.
by mariu52
1 subcomments
very cool! this article would have saved me quite some time if I discovered it earlier, as I ended up diving into a similar rabbit hole. Still, some useful tips I will incorporate into my emacs workflow, cheers for that.
one thing to add: I recommend piping the output to `xcbeautify` (https://github.com/cpisciotta/xcbeautify) to have sane build output; otherwise it's a mess outside of xcode.
Hacker News