search

emacs-helm / helm

Emacs incremental completion and selection narrowing framework
https://emacs-helm.github.io/helm/
GNU General Public License v3.0
3.36k stars 389 forks source link

Lisp nesting exceeds ‘max-lisp-eval-depth #2685

Closed algon-ns closed 3 weeks ago

algon-ns commented 3 weeks ago

What happened?

At Start of emacs [with (Debug on error t)] I get this error Lisp nesting exceeds ‘max-lisp-eval-depth from helm-core-20240830.1602/helm-core.el

How to reproduce?

Just starting emacs, but I am not smart enough to only have helm package loaded...... besides I think I need to have doom mode line runinng too.

I do not run Doom, but my own configuration

Helm Version

Master branch

Emacs Version

Emacs-30+

OS

MacOSX

Relevant backtrace (if possible)

Debugger entered--Lisp error: (error "Lisp nesting exceeds ‘max-lisp-eval-depth’")
  advice--p(#f(compiled-function (source &optional force) "Set up mode-line and header-line for `helm-buffer'.\n\nSOURCE is a Helm source object.\n\nOptional argument FORCE forces redisplay of the Helm buffer's\nmode and header lines." #<bytecode -0xbfe72b9abd9e863>))
  advice--tweak(#f(compiled-function (source &optional force) "Set up mode-line and header-line for `helm-buffer'.\n\nSOURCE is a Helm source object.\n\nOptional argument FORCE forces redisplay of the Helm buffer's\nmode and header lines." #<bytecode -0xbfe72b9abd9e863>) #f(compiled-function (first rest props) #<bytecode -0x1e8340da76c28075>))
  advice--remove-function(#f(compiled-function (source &optional force) "Set up mode-line and header-line for `helm-buffer'.\n\nSOURCE is a Helm source object.\n\nOptional argument FORCE forces redisplay of the Helm buffer's\nmode and header lines." #<bytecode -0xbfe72b9abd9e863>) doom-modeline-set-helm-modeline)
  #f(compiled-function (first rest props) #<bytecode -0x1e8340da76c28075>)(doom-modeline-set-helm-modeline #f(compiled-function (source &optional force) "Set up mode-line and header-line for `helm-buffer'.\n\nSOURCE is a Helm source object.\n\nOptional argument FORCE forces redisplay of the Helm buffer's\nmode and header lines." #<bytecode -0xbfe72b9abd9e863>) nil)
  advice--tweak(#f(advice doom-modeline-set-helm-modeline :after #f(compiled-function (source &optional force) "Set up mode-line and header-line for `helm-buffer'.\n\nSOURCE is a Helm source object.\n\nOptional argument FORCE forces redisplay of the Helm buffer's\nmode and header lines." #<bytecode -0xbfe72b9abd9e863>)) #f(compiled-function (first rest props) #<bytecode -0x1e8340da76c28075>))
  advice--remove-function(#f(advice doom-modeline-set-helm-modeline :after #f(compiled-function (source &optional force) "Set up mode-line and header-line for `helm-buffer'.\n\nSOURCE is a Helm source object.\n\nOptional argument FORCE forces redisplay of the Helm buffer's\nmode and header lines." #<bytecode -0xbfe72b9abd9e863>)) doom-modeline-set-helm-modeline)
  advice--add-function(:after (#f(compiled-function () #<bytecode 0x319866e3b41141>) . #f(compiled-function (gv--val) #<bytecode -0x10e36fc77a746659>)) doom-modeline-set-helm-modeline nil)
  advice-add(helm-display-mode-line :after doom-modeline-set-helm-modeline)
  doom-modeline-mode()
  run-hooks(doom-modeline-mode-hook doom-modeline-mode-on-hook)
  doom-modeline-mode()
  run-hooks(doom-modeline-mode-hook doom-modeline-mode-on-hook)
  doom-modeline-mode()
  run-hooks(doom-modeline-mode-hook doom-modeline-mode-on-hook)
......
 doom-modeline-mode()
  run-hooks(doom-modeline-mode-hook doom-modeline-mode-on-hook)
  doom-modeline-mode()
  run-hooks(after-init-hook delayed-warnings-hook)
  command-line()
  normal-top-level()

Minimal configuration

thierryvolpiatto commented 3 weeks ago

Niels Søndergaard @.***> writes:

What happened?

At Start of emacs [with (Debug on error t)] I get this error Lisp nesting exceeds ‘max-lisp-eval-depth from helm-core-20240830.1602/helm-core.el

How to reproduce?

Just starting emacs, but I am not smart enough to only have helm package loaded......

Most of the helm bugs come from an emacs configured with either spacemacs or doom, this is why I ask people to start with emacs-helm.sh. It is really simple to do.

besides I think I need to have doom mode line runinng too.

Looks it is not Helm but doom-modeline-mode that cause the bug.

I do not run Doom, but my own configuration

Your configuration IS using doom apparently.

Of course the bug is not reproductible here.

-- Thierry

thierryvolpiatto commented 3 weeks ago

Please contact the Doom maintainer for your bug which is not related to Helm. For help feel free to ask at https://github.com/emacs-helm/helm/discussions.

Thanks.

algon-ns commented 3 weeks ago

thanks for your info: after taking my configuration out of my configuration, I make a new (as far as I can see exactly like the one deleted), and then it worked. weird

med venlig hilsen Niels

Den 4. sep. 2024 kl. 07.35 skrev Thierry Volpiatto @.***>:

Closed #2685 https://github.com/emacs-helm/helm/issues/2685 as completed.

— Reply to this email directly, view it on GitHub https://github.com/emacs-helm/helm/issues/2685#event-14124444508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN7YBR3M3ONFK6KF6FNPITLZU2LYNAVCNFSM6AAAAABNRBXCTCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGEZDINBUGQ2TAOA. You are receiving this because you authored the thread.