Respect helm-buffer-max-length if it's nil #173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't overwrite helm-buffer-max-length when it's nil, because nil indicates that we should use the max length of the longest file every time.
This code is now the same as what helm-buffers does: https://github.com/emacs-helm/helm/blob/8ed0ab7762ad76da02d8832aa18d03e1288ea6d5/helm-buffers.el#L300
You can reproduce the issue by setting helm-buffer-max-length to nil, opening helm projectile, and then opening helm buffer and seeing that the files in the buffer may be getting cut off if the longest file in helm projectile is shorter.
This is just a drive-by PR and I've fixed the problem on my end, so I haven't checked the boxes below. If it's too much extra work on your end, no need to merge. Thanks!!
Before submitting a PR make sure the following things have been done (and denote this
by checking the relevant checkboxes):
M-x checkdoc
warningsThanks!