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.67k stars 4.89k forks source link

auto-completion keybindings broken in vanilla config #11070

Closed manveru closed 4 years ago

manveru commented 6 years ago

Description :octocat:

Completion is broken in interesting ways, I haven't checked all keybings, just the ones I usually use, and they're all broken.

I also tried going back in the develop branch history, since I'm sure it worked at some point, but couldn't find any commit that did.

Reproduction guide :beetle:

Observed behaviour: :eyes: :broken_heart:

Expected behaviour: :heart: :smile:

System Info :computer:

Backtrace :paw_prints:

None

manveru commented 6 years ago

Just checked, and it happens even if you only enable the auto-completion and emacs-lisp layer in spacemacs-base distribution... Am I really the only one affected by this bug?

manveru commented 6 years ago

So it seems like the C-n/C-d issue can be fixed by putting

(define-key company-active-map (kbd "C-n") 'company-select-next)
(define-key company-active-map (kbd "C-p") 'company-select-previous)

in the dotspacemacs/user-config, but C-d behavior is still broken.

Miciah commented 6 years ago

Your report says that you are using the vim editing style; in this style, you should use C-j and C-k rather than C-n and C-p. See http://develop.spacemacs.org/layers/+completion/auto-completion/README.html#company.

It looks like there is an issue with C-d though.

manveru commented 6 years ago

Thanks, I just noticed that i was using hybrid style in my old working config, that might've made the difference.

manveru commented 6 years ago

Yeah, just confirmed that switching to hybrid style in a vanilla config makes everything work again. I guess there's still a bug with vim style, but it doesn't affect me anymore.

github-actions[bot] commented 4 years ago

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!