UPDATE: append available battery types

[dev-onejun]

Hello,

I had a problem presenting the battery value on my laptop.

In order to solve the problem, I added my laptop battery type in the linux.vim file.

Since I experienced similar problem in an another project, I applied a same solution.

• Enhancement: Regarding Support Multiple Types of Batteries dracula/tmux#244

Thank you.

Summary by CodeRabbit

• New Features
  • Expanded battery type support in the Linux backend, allowing for a broader range of battery directories to be recognized.

[coderabbitai]

Walkthrough

The update enhances the Linux backend script for battery monitoring by broadening the search criteria for battery directories. It introduces an additional pattern, 'CMB*', to accommodate a wider range of battery types, ensuring more comprehensive battery support across different Linux systems.

Changes

File	Change Summary
autoload/battery/.../linux.vim	Expanded search pattern for battery directories to include 'CMB*' option.

🐰✨
In the land of code and vim,
A rabbit hopped, its chances slim.
It sought to make the batteries found,
By patterns wide and bounds unbound.
'CMB*' it whispered, a spell so bright,
Now every battery comes to light.
🌟🔋

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 596a79c and 1e09b7a.

Files selected for processing (1)

• autoload/battery/backend/linux.vim (1 hunks)

Additional comments: 2

autoload/battery/backend/linux.vim (2)

• 2-2: The search pattern for battery directories has been expanded correctly to include 'CMB*' as an additional option. This change effectively broadens the script's compatibility with different battery types. Ensure that the inclusion of 'CMB*' does not conflict with any existing patterns or expected directory structures on Linux systems.
• 1-5: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [3-20]

The overall structure and logic of the file remain sound following the change. The functions for reading battery information, updating it, defining the backend, and checking availability are well-implemented and maintain good practices for readability and maintainability. The change to the search pattern integrates seamlessly without affecting the core functionality.

[lambdalisue]

Thanks 🎉