it takes some time to get used to it (evil-lisp-state). I do want to hate it sometimes, but then I quickly remember that I’m actually too lazy to find anything better.

@jstew if you only ever use Spacemacs in holy mode then I would recommend sticking to Smartparens in strict mode (or paredit if you prefer). If you are learning to take advantage of the multi-modal approach in Spacemacs evil mode, then I suggest that lisp mode, especially lisp mode transient state, is well worth learning. This suggestion assumes you are regularly working with a structured language like elisp, lisp, clojure, etc. Thanks.

@jr0cket - Thank you... Were you the person who made a clojure/spacemacs guide? If so, nice work!

@jstew link to guide?

http://jr0cket.co.uk/2015/09/spacemacs-for-clojure-development-configure-clojure.html

I am assuming that's the same person 😄

Also found : https://practicalli.github.io/spacemacs/

Oh nice, I haven't read this one yet

very nice. As I'm just starting to learn Clojure, this seems to be a good resource.

After ~1 year, I still love spacemacs, but it's gradually gotten a bit painfully slow over time (slow enough that it doesn't consistently keep up with my SPC-WHATEVER keystrokes...). Anyone here had much luck tracking down slowdown causes? Asking here since it could easily be one of the minor modes that clj/s folks install...

One thing that's helped a bit is setting dotspacemacs-which-key-delay 0.01

Thanks for the positive feedback on the practicalli Spacemacs book, I awill be adding more over the next few days and weeks

I found that it is the smooth scrolling, relative line numbering and the parsing of every little thing in your file that slows Spacemacs down (parsing for: syntax highlighting, syntax checking and definition lookup). There is a way to let a profiler run while you work in Spacemacs (the profiler is built in) and then analyze what is happening in the background. But I forgot how to start the profiler. perhaps run Spacemacs in debug mode or do a M-x profile-search. or both. But it is usually all the parsing of the code that uses up your CPU cycles 🙂

@eggsyntax - I have that issue too, it goes away when I close emacs, comes back when I work on multiple projects, especially ones with TAGS files in them. The worst is company-mode completing a string. Installing aspell on my system has helped a little bit with that.

@jstew @eggsyntax @sebastian Have you already tried to use ivy instead of helm? It quite improved Spacemacs’ behaviour for me.

Yes. I found it to give a slight improvement but I like helm more, so I switched back.

true indeed, ivy has less features than helm. but for me the improvement of speed warranted the switch to ivy.

@sebastian thanks, good tips! Haven't started w/ the profiler yet, but that's my plan. @jstew cool, thanks, I mostly stick to one project per instance. Don't think I have TAGS files in it, but I'll have to double-check. There's definitely a huge difference between some projects and others, which makes me suspect projectile a bit. But yeah, string completion is clearly a problem, I'll try aspell. & ivy too, I've been considering giving that a shot. Many thanks, y'all!

Hmm. @jstew does aspell replace auto-completion, though? Looks like it's more focused on spell-checking, & not seeing anything in its docs about completion.

spell check is a source of auto-completion in some modes. I know that it helped immensely with org-mode. I didn't notice a difference with Clojure.