Skip to content

fix: Hide when on a desktop #354

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

lfreixial
Copy link
Contributor

Moved the check of the battery percentage to the top as it was always hitting the $bat_stat check making it to never hide the label and always display a <3

Copy link

coderabbitai bot commented Jul 19, 2025

📝 Walkthrough

Walkthrough

The changes remove the configuration option and logic for hiding the battery widget on desktop PCs. Documentation describing the @dracula-battery-hide-on-desktop option is deleted, and the battery script no longer checks for this setting, instead simplifying its conditional output logic.

Changes

File(s) Change Summary
docs/CONFIG.md Removed documentation for the @dracula-battery-hide-on-desktop configuration option.
scripts/battery.sh Eliminated logic for the hide-on-desktop option; simplified battery status output conditions.

Possibly related PRs


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9fa47b and 281b8c2.

📒 Files selected for processing (1)
  • scripts/battery.sh (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • scripts/battery.sh
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
scripts/battery.sh (1)

175-178: Strip the leading space when the battery label is disabled.

If @dracula-battery-label is set to false, bat_label becomes an empty string.
The current branch will emit " $bat_perc" (note the leading space).
A tiny tweak avoids the extra whitespace:

-  elif [ -z "$bat_stat" ]; then # Test if status is empty or not
-    echo "$bat_label $bat_perc"
+  elif [ -z "$bat_stat" ]; then # Test if status is empty or not
+    # Only add a space when the label is not empty
+    if [ -n "$bat_label" ]; then
+      echo "$bat_label $bat_perc"
+    else
+      echo "$bat_perc"
+    fi
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d85b265 and c9fa47b.

📒 Files selected for processing (2)
  • docs/CONFIG.md (0 hunks)
  • scripts/battery.sh (1 hunks)
💤 Files with no reviewable changes (1)
  • docs/CONFIG.md
🔇 Additional comments (1)
scripts/battery.sh (1)

175-178: LGTM – re-ordering fixes the desktop/AC detection bug.

The early bat_perc check now short-circuits correctly when no battery is present. 👌

@Theoreticallyhugo
Copy link
Collaborator

Theoreticallyhugo commented Jul 20, 2025

hi, now i must apologize because you're putting in the effort and i'm asking you to do more 😅

would you mind testing #348 where i'm making major changes to the battery script?
i would recommend setting

# setting no label
set -g @dracula-battery-label false
set -g @dracula-no-battery-label false

to get no output.

though to be fair that would kinda limit reusability of the same config on different machines in the sense that you either have a label which will prevent the plugin from disappearing on desktop, or you remove the label and thus can't have it on the laptop either.
i'm open to discussing whether this is an issue we need to fix, or whether thats an ok restriction

@lfreixial
Copy link
Contributor Author

@Theoreticallyhugo It's no worries at all! I've just tested it and it works completely fine.

I added this on both my desktop and laptop

set -g @dracula-battery-label false
set -g @dracula-no-battery-label false
set -g @dracula-show-battery-status true

and on my desktop the battery widget disappears while on the laptop it has the battery icon and percentage still, so the same config can still be used on both devices.

Feel free to close this PR out (or I can do it if its easier) and also feel free to remove the other code I added on #354 .

Thank you!

@Theoreticallyhugo
Copy link
Collaborator

thank you very much for your help!
i'll manage everything when i got time and hopefully remember to ping you so that you know when the master branch is ready :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants