<SPC k> is unconveniently reserved for lisp code

[PierreR]

The pink state aka Lisp code state (as the name implies) is meant for editing lisp files.

Because it quickly shows up when trying SPC k I have tried to exclude the evil-lisp-state package.

Then to my surprise SPC k was no more available anymore.

This is a bit unfortunately because:

• some smartparens keybindings useful for every file type could be made available there. For instance I miss a binding for sp-unwrap-sexp.
• SPC k name does not imply lisp, does it ?

Could the lisp code state be made less easily accessible and SPC-k reserved for general smartparensand other related features that work across all file type ?

[syl20bnr]

lisp state already include functions that works in all modes under SPC k ``. sp-unwrap-sexpis underSPC k W` I believe.

[PierreR]

lisp state already include functions that works in all modes under SPC k `

Well that's what I am complaining about. We have something specific (the lisp state mode) that works for all modes sometimes. This is quite confusing. You quickly end up in a pink state that makes no sense for non-lisp files.
I believe every functionally behind SPC k should be generic, what is specific for lisp file less easily accessible. In that regard, I should be able to exclude the evil-lisp-state package and still be able to use the generic functionalities (for instance keybindings from smartparens).

[Spadavecchia]

Was SPC k removed? I'm trying use it, but is not assigned. In documentation there is reference to shortcut. https://github.com/syl20bnr/spacemacs/blob/master/doc/DOCUMENTATION.org#editing-lisp-code

[TheBB]

It's not removed, but please make sure you are fully updated, both Spacemacs and packages, as some changes were made to it recently.

[Spadavecchia]

I updated Spacemacs and nothing. Delete it and reinstall. Now all is working again. Thank you.
Amazing work by the way.

[TheBB]

Good 👍. Note that when I say update both Spacemacs and packages it's not enough to just update Spacemacs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!