syl20bnr / spacemacs

A community-driven Emacs distribution - The best editor is neither Emacs nor Vim, it's Emacs *and* Vim!
http://spacemacs.org
GNU General Public License v3.0
23.59k stars 4.9k forks source link

New encryption shortcuts clash with Evernote layer #13496

Closed choffee closed 4 years ago

choffee commented 4 years ago

Description :octocat:

New encryption shortcuts clash with Evernote layer

This commit added some new shortcuts under a-e which clashes with the evernote layer ones. https://github.com/syl20bnr/spacemacs/commit/1055baafa29ed89f7658604d91c92067763416fc

Reproduction guide :beetle:

Observed behaviour: :eyes: :broken_heart: Warning (initialization): An error occurred while loading ‘/home/john/.emacs.d/init.el’:

error: Key sequence a e s r starts with non-prefix key a e s

To ensure normal operation, you should investigate and remove the cause of the error in your initialization file. Start Emacs with the ‘--debug-init’ option to view a complete error backtrace. Expected behaviour: :heart: :smile: Clean startup :)

System Info :computer:

Backtrace :paw_prints:

<<BACKTRACE IF RELEVANT>>
choffee commented 4 years ago

Hrumph, /me goes to change wakatime api key....

practicalli-johnny commented 4 years ago

Sorry, didnt know SPC a e was already taken. I did ask for feedback on the right keybindings to use in #13319

The alternative key binding for Easy PG I suggested was SPC E. Or to keep it in applications, the key binding SPC a g could be used and labelled gpg.

Is there any way to see a list key bindings under SPC a that are used in layers. I assume some sort of search in the git project.

/cc @smile13241324

smile13241324 commented 4 years ago

Looks like we have some conflicts in the global bindings from various layers. I have made this list from helm, scanning the bindings in all the README.org files in the layer directory.

+chat/jabber/README.org:31:| ~SPC a j~
+chat/erc/README.org:107:| ~SPC a i~  ---> No conflict both are using different sub level bindings
+chat/rcirc/README.org:235:| ~SPC a i~ --> Same here
+chat/slack/README.org:69:| ~SPC a C~
+emacs/org/README.org:358:| ~SPC a o~
+email/gnus/README.org:146:| ~SPC a g~
+email/mu4e/README.org:67:| ~SPC a M~
+email/notmuch/README.org:100:| ~SPC a N~
+fun/emoji/README.org:38:| ~SPC a E~
+fun/games/README.org:39:| ~SPC a G~
+fun/xkcd/README.org:34:| ~SPC a x~
+lang/ipython-notebook/README.org:73:bound to ~SPC a y~
+music/pianobar/README.org:56:| ~SPC a m~  ----> No conflict both are using different sub level bindings
+music/spotify/README.org:35:| ~SPC a m~ -----> Same here
+readers/deft/README.org:62:| ~SPC a n~
+readers/elfeed/README.org:112:| ~SPC a f~
+readers/speed-reading/README.org:26:| ~SPC a R~
+readers/dash/README.org:26:| ~SPC a z~
+tools/bm/README.org:36:| ~SPC a b~
+tools/chrome/README.org:74:| ~SPC a F~
+tools/command-log/README.org:28:| ~SPC a L~
+tools/docker/README.org:79:| ~SPC a D~
+tools/geolocation/README.org:119:| ~SPC a w~ ----> Layer uses two prefixes should be changed to use w only
+tools/geolocation/README.org:120:| ~SPC a W~ ----> Same
+tools/kubernetes/README.org:47:| ~SPC a K~
+tools/pass/README.org:28:| ~SPC A p~ -----> Layer is using wrong menu should use a instead of A
+tools/prodigy/README.org:38:| ~SPC a S~
+tools/quickurl/README.org:28:| ~SPC a Q~
+tools/ranger/README.org:128:| ~SPC a r~
+tools/ranger/README.org:129:| ~SPC a d~
+tools/shell/README.org:294:| ~SPC a s~
+tools/transmission/README.org:62:| ~SPC a t~
+tools/vagrant/README.org:21:- ~SPC a V~
+web-services/evernote/README.org:58:| ~SPC a e~
+web-services/search-engine/README.org:56:| ~SPC a /~

I think we should move Easy pg to SPC a Y this would use the y from easy pg as memonic as e and s are already taken.

smile13241324 commented 4 years ago

@choffee @jr0cket I have moved the bindings accordingly. The global application bindings should not longer clash. As we are getting more and more members in that group we will have to eventually group them based on categories like it has been done for music and irc. But this is something for a different PR.

For now please double check on latest develop and close this issue when the conflicts are gone.

choffee commented 4 years ago

That has fixed it for me. Thank you.