doomemacs / doomemacs

An Emacs framework for the stubborn martian hacker
MIT License
19.39k stars 3.05k forks source link

Doom Keybindings not working #7675

Closed huNt-FMJ closed 8 months ago

huNt-FMJ commented 8 months ago

I confirm that...

Expected behavior

When I press SPC RET, my list of book marks should be shown

Current behavior

When I press SPC RET, the echo area states: [2024-02-14 17:44:15] SPC RET is undefined

There is no error, no stacktrace, and no hint in the *Messages* buffer.

Pressing SPC gives me only two options: image

doom doctor gives:

The doctor will see you now...

> Checking your Emacs version...
> Checking for Doom's prerequisites...
> Checking for Emacs config conflicts...
> Checking for missing Emacs features...
> Checking for private config conflicts...
> Checking for common environmental issues...
> Checking for stale elc files...
> Checking for problematic git global settings...
> Checking Doom Emacs...
  ✓ Initialized Doom Emacs 3.0.0-pre
  ✓ Detected 53 modules
  ✓ Detected 219 packages
  > Checking Doom core for irregularities...
    Found font NFM.ttf
  > Checking for stale elc files in your DOOMDIR...
  > Checking your enabled modules...
    > :lang clojure
      ! Couldn't find clj-kondo. flycheck-clj-kondo will not work.
    > :lang go
      ! Couldn't find gopls.
      ! Couldn't find gomodifytags. Manipulating struct tags will not work
      ! Couldn't find gotests. Generating tests will not work
      ! Couldn't find gore. REPL will not work
      ! Couldn't find guru. Refactoring commands (go-guru-*) won't work
    > :lang kotlin
      ! ktlint not found. flycheck-kotlin won't work.
    > :lang markdown
      ! Couldn't find a markdown compiler, `markdown-preview' won't work
    > :lang python
      ! Couldn't find isort. Import sorting will not work.
      ! Couldn't find pipenv. pipenv support will not work.
      ! Couldn't find nosetests. Running tests through nose will not work.
      ! Couldn't find pytest. Running tests through pytest will not work.
      ! setuptools wasn't detected, which anaconda-mode requires
    > :lang rust
      ! Couldn't find rust analyzer (rust-analyzer)
      ! Couldn't find rustc binary
    > :lang web
      ! Couldn't find tidy. Code formatting in HTML modes will not work.
      ! Couldn't find stylelint. Linting for CSS modes will not work.
      ! Couldn't find js-beautify. Code formatting in JS/CSS/HTML modes will not work.
    > :email mu4e
      ! Couldn't find mu command. Mu4e requires this to work.

There are 19 warnings!

doom run --debug-init gives:

doom run --debug-init
Loading /home/x/.config/emacs/lisp/doom.el (source)...
Loading /home/x/.config/emacs/lisp/doom.el (source)...done
* 0.010649:*:load: doom-start nil
* 0.013100:*:hook:doom-before-init-hook: run doom--begin-init-h
* 0.013125::context: +init (t)
* 0.013460:*:init:load: /home/x/.config/doom/init t

Steps to reproduce

  1. Open doom emacs
  2. press SPC <doom key>
  3. See SPC <doom key> is undefined

System Information

https://gist.github.com/huNt-FMJ/ecd3676b8f6fa74001ef7fdbf28945a8

hlissner commented 8 months ago

When keybinds go missing, it's because there is an unaddressed (and often unrelated) error while Emacs is starting up. Please use the tools mentioned in the debugging guide to find them. The first thing to try being: C-h e (M-x view-echo-area-messages) to see the *Messages* buffer. Search for error messages, and if you find one, try to produce a backtrace for it (see "Dealing with errors" at the Discourse link above).

EDIT: My bad, had a knee-jerk reaction to the title and missed the "no hint in the Messages buffer" tidbit (I get a lot of these "keybindings are broken" reports).

That said, looking at your doom-info, it says you don't have the :config (default +bindings) module enabled (where the leader keys like SPC RET are bound). You may want to check your doom! block in $DOOMDIR/init.el for typos.

huNt-FMJ commented 8 months ago

Will check, thank you.

huNt-FMJ commented 8 months ago

Dead on. Thanks a ton.