Don't care about your platform, desktop (I'm typically working over SSH in the cloud, so why bother?) or any of that hooplah.
Just waiting for everybody else to catch up.
The problem is that the 'stable/master' branch of Spacemacs is incredibly outdated. I found myself needing fixes or improvements that existed in 'develop' so often that I migrated over to that branch. The idea of regularly cutting stable releases just isn't done within that project so if I'm recommending Spacemacs to new users I have to give them installation instructions that aren't provided by the documentation. Also, to get more up to date documentation I need to go to the layers docs in the GitHub repo and that can be hard to track down.
Every fresh install I've setup there has just been... so many problems with melpa and pulling down packages. Most of the time I have to repeatedly delete the package cache and restart Emacs until Spacemacs successfully pulls down packages - usually using the insecure flag so that packages aren't downloaded over HTTPS.
It's just... not as a polished as installing VSCode and a bunch of extensions. Spacemacs can require a lot of work and patience and I've just had too many things break with it over time.
I also frequently wonder how I'd introduce spacemacs to someone who hasn't used vim or emacs... I used vim for a very long time, so to me it's great that my knowledge carries over. I just don't know if it makes complete sense to say to someone "vim has better bindings than emacs, so even though this is emacs, you should learn these vim binds". Plus then they should probably still know at least the basics of emacs for screens where evil fails you, or for if they ever have to use emacs on another machine, or for when an emacs bind is better ("C-x h" seems better than ggVG to me).
i really _want_ to use it. I love vim's modal editing, but extending vim is a pain in the butt, and I'd love to use lisp to tweak my editor.
But, I absolutely can not recommend spacemacs right now.
Installation process is broken crap (at least on the mac) and you end up having to deal with meta-this-that-the-other way too often for simple (non-advanced) vim commands.
I do use `:e` and `:w` pretty often, so I'm grateful those work. I suppose I would've felt very differently if I'd ran into issues with them early on. I don't actually use `:q` from spacemacs since with emacs you often leave open all your visited files. If I do want to get rid of something, I tend to do `SPC b d` for buffer delete.
>installation doesn't work
I think on my GNU/Linux machine the installation worked for me. I first started switching to the develop branch because of a bug in one of the layers I enabled that was fixed in develop.
>insecure downloads
I definitely haven't made this change that people are mentioning.
Is there a nice how-to for setting up emacs with evil mode and a reasonable set of defaults that don’t require endless tweaking?
Being able to remotely open my editor (either from a terminal, or with X11 forwarding) with all the files I have open, exactly where I left off is incredibly useful.
A few years ago, I started using one daemon per project with server-use-tcp, each with a slightly different theme so I can easily tell them apart.
(posted from emacs-w3m)
Other big benefit is starting emacsclient is basically instant, so opening a file from a webbrowser or whatever is super fast (some folks have 30 second or longer emacs startup times).
Only real downside is it really sucks bringing back your state when emacs crashes and you have hundreds of buffers open for multiple projects across 20-30 emacs clients.
I have see this many times and never understood how startup time could be an issue. I startup Spacemacs at the beginning of the day, and close it when I leave. 10 second of startup time is nothing.
Then again it may be the case that part of the cycle is seeing if the package management system of your custom distro (be it spacemacs, doom, or whatever) picks up and configures the new packages correctly.
Some modes also support limited refactoring tools[2], but that's not quite as common.
[1] https://www.gnu.org/software/emacs/manual/html_node/emacs/Xr...
[2] https://github.com/clojure-emacs/clj-refactor.el, https://github.com/Wilfred/emacs-refactor, https://www.emacswiki.org/emacs/SemanticRefactor
It's a great time to be alive
Happy sigh...those were the days :-)
It's hard to beat an IDE on a large, disorganised codebase though, I'd lie if I said I only use Emacs and never reach out for an IDE.
It's not as sophisticated as an IDE, but it works with practically any language and is easy to customize.
I find it often quicker than an IDE..
What they usually can't do is the more involved stuff, like refactoring, because there is no company who pays people to implement these for emacs/vim.
It's true that funding is important. CIDER has benefited from this system: https://www.clojuriststogether.org/projects/
After learning vim, I couldn't stand using nano. It seemed like the worst of both worlds. No efficient keybindings like vim, and no mouse support like other conventional text-areas.
Hearing/reading you say that you sometimes use nano made me curious of why and now I see that there seems to actually be quite a few features. I see it has macros, autocomplete, mouse support, autoindent, multiple buffers, editing keybindings to e.g. delete word-wise, linting support, etc.
I never knew... and totally misjudged it as a very basic text editor.
It's still basic when compared with vim or emacs, but now I hold it in far higher regard than Windows Notepad at least.
I kind of feel like that time many years ago I found out that sed had more than just s///.
I run emacs-plus macOS variant, which one are you running?
brew install emacs
brew install emacs --HEAD
brew install emacs --with-cocoa --with-imagemagick@6 --HEAD
brew install emacs --with-librsvg --with-cocoa --with-imagemagick@6 --HEAD
brew install emacs --with-gnutls --with-librsvg --with-
cocoa --with-imagemagick@6 --HEAD
brew install emacs --devel --with-cocoa --with-gnutls --with-librsvg --with-imagemagick
brew install emacs --HEAD --use-git-head
brew install emacs-plus --HEADWith Emacs that means Ensime, and Emacs becomes just as slow as VSCode+Metals or IntelliJ.
ACME's plumber is very cool, and allows very easy customization of how some things work. Much easier than these things typically are in Emacs. But this behavior is implementable in Emacs (I wish it were standard), and lots of things that are hard-coded in ACME are fully customizable in Emacs.
Interestingly, the first Emacs "plumber" which I have found after you wrote it literally uses Acme's plumber: https://github.com/alcah/sink.el
I wish Emacs had 9P support though.
Emacs had been my work horse since 2002 and never disappointed. In the meantime tried many ide only vim and emacs stayed with me. Sometimes do use nano and sublime text but then back to either emacs or vi.
All those shiny IDE based on electron, Java or C++ are just too slow to be productive be it VScode, atom or eclipse or visual studio or kdevelop. I am forced to use them due to tooling support for some framework. But I avoid them as much as possible once I have configured emacs to work with the language or sdk or framework or library in question.