Setting completions-detailed to t breaks kill-buffer command when helm-buffer-max-length is set to nil

[cloudchin]

What happened?

Hey Thierry

I don't know the use-case of helm-buffer-max-length or why I had it in my config to begin with, but having it set to nil with completions-detailed enabled breaks kill-buffer returning Wrong type argument: number-or-marker-p, nil

How to reproduce?

With this config

(require 'helm)
(require 'helm-autoloads)
(helm-mode 1)
(setq helm-buffer-max-length nil
      completions-detailed t)

and try C-x k

Alternatively, set those variables in an emacs-helm.sh session and C-x k

Helm Version

Master branch

Emacs Version

Emacs-29.1

OS

GNU/Linux

Relevant backtrace (if possible)

Minimal configuration

• I agree using a minimal configuration

[thierryvolpiatto]

cloudchin ***@***.***> writes:

What happened? Hey Thierry I don't know the use-case of helm-buffer-max-length

See its docstring.

or why I had it in my config to begin with, but having it set to nil with completions-detailed enabled breaks kill-buffer returning Wrong type argument: numper-or-marker-p, nil

The error say all, helm-buffer-max-length should be a number... It is protected in helm-buffers where it was used originally but not in helm-mode, it is now fixed. Thanks.

…

-- Thierry