Unable to read help `C-h` minibuffer bottom text line

[RidaAyed]

Description :octocat:

Unable to read help C-h minibuffer bottom text line

Reproduction guide :beetle:

• Start Emacs
• Hit C-h

Observed behaviour: :eyes: :broken_heart:

Expected behaviour: :heart: :smile: Can read all text lines

System Info :computer:

• OS: gnu/linux
• Emacs: 29.3
• Spacemacs: 0.999.0
• Spacemacs branch: develop (rev. d36038f5c)
• Graphic display: t
• Running in daemon: t
• Distribution: spacemacs
• Editing style: vim
• Completion: helm
• Layers:

  ((spacemacs-layouts :variables spacemacs-layouts-restrict-spc-tab t)
  systemd graphviz
  (spell-checking :variables spell-checking-enable-by-default nil spell-checking-enable-auto-dictionary t enable-flyspell-auto-completion t)
  (yaml :variables yaml-enable-lsp t)
  (json :variables json-fmt-tool 'web-beautify)
  latex pass csv prodigy
  (treemacs :variables treemacs-use-all-the-icons-theme t)
  search-engine
  (auto-completion :variables auto-completion-enable-snippets-in-popup t auto-completion-enable-help-tooltip t auto-completion-return-key-behavior 'complete auto-completion-tab-key-behavior 'cycle auto-completion-enable-sort-by-usage t auto-completion-idle-delay 0.2 auto-completion-minimum-prefix-length 2)
  exwm emacs-lisp git helm finance
  (org :variables org-enable-hugo-support t org-enable-github-support t)
  (shell :variables shell-default-shell 'ansi-term shell-default-height 30 shell-default-position 'right spacemacs-vterm-history-file-location "~/.bash_history")
  (version-control :packages
                (not git-gutter))
  mu4e pdf
  (python :variables python-backend 'lsp python-lsp-server 'pyright python-test-runner 'pytest))

• System configuration features: ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG JSON LCMS2 LIBOTF LIBSYSTEMD LIBXML2 M17N_FLT MODULES NOTIFY INOTIFY PDUMPER PNG RSVG SECCOMP SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER WEBP X11 XDBE XIM XINPUT2 XPM GTK3 ZLIB

Backtrace :paw_prints:

<<BACKTRACE IF RELEVANT>>

[fnussbaum]

I cannot exactly reproduce this, but you could try increasing the value of which-key-side-window-max-height in case your font size is large compared to the height of the screen/window. By default the which-key window uses at most one quarter of the height.