Symbol’s value as variable is void: helm-source-occur

[nyambol]

Expected behavior

Helm to load normally

Actual behavior (from emacs-helm.sh if possible, see note above)

Compile errors from reinstalling via package.el.

Compiling file c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-buffers.el at Mon Jul  5 13:18:31 2021
helm-buffers.el:24:1:Error: Symbol’s value as variable is void: helm-source-occur

Compiling file c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-color.el at Mon Jul  5 13:18:31 2021
helm-color.el:22:1:Error: Symbol’s value as variable is void: helm-source-occur

Compiling file c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-comint.el at Mon Jul  5 13:18:31 2021
helm-comint.el:31:1:Error: Symbol’s value as variable is void: helm-source-occur

Compiling file c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-command.el at Mon Jul  5 13:18:31 2021
helm-command.el:23:1:Error: Symbol’s value as variable is void: helm-source-occur

Steps to reproduce (recipe)

Unknown. Helm worked fine until I installed helm-google, helm-ag, and helm-swoop. After restarting emacs, this error started occurring. I removed those packages, deleted helm and helm-core directories and reinstalled them. The error occurs during the byte-compiling of the installation, as indicated above.

I was using use-package. It was working fine, until it wasn't.

(use-package helm
  :ensure t
  :config
  (helm-mode)
  (setq completion-styles '(flex))
  (helm-popup-tip-mode))

Backtraces if any (M-x toggle-debug-on-error)

Starting emacs without any helm setup, then M-x helm-mode:

Debugger entered--Lisp error: (void-variable helm-source-occur)
  #f(compiled-function () #<bytecode 0x240ef9d>)()
  funcall(#f(compiled-function () #<bytecode 0x240ef9d>))
  mapc(funcall (#f(compiled-function () #<bytecode 0x240ef9d>)))
  do-after-load-evaluation(""c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-regexp.elc"")
  require(helm-regexp)
  eval-buffer(#<buffer  *load*-469412> nil "c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-grep.el" nil t)  ; Reading at buffer position 904
  load-with-code-conversion("c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-grep.el" "c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-grep.el" nil t)
  require(helm-grep)
  eval-buffer(#<buffer  *load*-788377> nil "c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-files.el" nil t)  ; Reading at buffer position 913
  load-with-code-conversion("c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-files.el" "c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-files.el" nil t)
  require(helm-files)
  eval-buffer(#<buffer  *load*> nil "c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-mode.el" nil t)  ; Reading at buffer position 892
  load-with-code-conversion("c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-mode.el" "c:/Users/micha/AppData/Roaming/.emacs.d/elpa/helm-20210701.637/helm-mode.el" nil t)
  (helm-mode)
  eval((helm-mode) nil)
  elisp--eval-last-sexp(nil)
  eval-last-sexp(nil)
  funcall-interactively(eval-last-sexp nil)
  #<subr call-interactively>(eval-last-sexp nil nil)
  apply(#<subr call-interactively> eval-last-sexp (nil nil))
  call-interactively@ido-cr+-record-current-command(#<subr call-interactively> eval-last-sexp nil nil)
  apply(call-interactively@ido-cr+-record-current-command #<subr call-interactively> (eval-last-sexp nil nil))
  call-interactively(eval-last-sexp nil nil)
  command-execute(eval-last-sexp)

Describe versions of Helm, Emacs, operating system, etc.

Version helm-20210701.637 Emacs 27.2 Windows 10 Pro

Are you using emacs-helm.sh to reproduce this bug? (yes/no):

no, it does not occur when running the script version.

[nyambol]

I have found the offender. It's the package all-ext. Loading it either before or after the loading of helm, it produces the subject error during emacs startup-init.

[thierryvolpiatto]

Great, so I am closing now.