“Too many files open?” Not anymore.

Our past release included improvements when it comes to LSP. Some users notified us about a regression where Crush would error with "too many files open". This was happening in particular when opening Crush inside a directory with several files, which could be a big monorepo or $HOME, for example. We've done a fix for it, but we know it can still happen in some scenarios. The next release will likely include further enhancements in the area.

Thanks for your awesome support!

Changelog

Bug fixes and improvements

• 9a132dc: fix: introduce notify ignore files (@raphamorim)
• de3d46b: fix: make the limit really high on non-unix (@raphamorim)
• fd6b617: fix: remove ulimt as go 1.19 automatically raises file descriptors (@raphamorim)
• d401aa3: fix: request MaximizeOpenFileLimit for unix (@raphamorim)
• 8cae314: fix: windows lint for number (@raphamorim)
• 7ff6ba9: refactor: make func unexported (@andreynering)

Other work

• 6ec5a77: chore: update github.com/raphamorim/notify to v0.9.4 (@andreynering)
• 18ea1c9: handle ctx cancel event (@vadiminshakov)

wget 'https://github.com/charmbracelet/crush/releases/download/v0.8.2/checksums.txt'

cosign verify-blob \
  --certificate-identity 'https://github.com/charmbracelet/meta/.github/workflows/goreleaser.yml@refs/heads/main' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
  --cert 'https://github.com/charmbracelet/crush/releases/download/v0.8.2/checksums.txt.pem' \
  --signature 'https://github.com/charmbracelet/crush/releases/download/v0.8.2/checksums.txt.sig' \
  ./checksums.txt

sha256sum --ignore-missing -c checksums.txt

Thoughts? Questions? We love hearing from you. Feel free to reach out on X, Discord, Slack, The Fediverse, Bluesky.