Skip to content

patch: spotify and apple-music backtrack conflicts with remote control and display optimizations #355

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

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

iberniex
Copy link
Contributor

@iberniex iberniex commented Jul 19, 2025

This patch contains solutions to errors (which were caused by my bad coding):

  • the back track option for applescript is only for apple-music but spotify it doesn't have it. I've added a guard to the back variable thus the spotify option is set to previous track
  • boolean values patched to strings
  • cache optimizations
  • not overusing the cat command

iberniex added 6 commits July 19, 2025 17:03
This patch is related to the spr plugin remote option in which it was
conflicting with the mac-player plugin in which it was displaying the
osascript scripts from this plugin.
… spotify

there was error of using the R keybind that was not working with spotify
and leading to the issues of spotify not working well.
catting the cache file alot of times would leading to increased latency.
Copy link

coderabbitai bot commented Jul 19, 2025

Warning

Rate limit exceeded

@iberniex has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 2 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 40ce9b7 and d640a18.

📒 Files selected for processing (1)
  • scripts/mac-player.sh (2 hunks)
📝 Walkthrough

Walkthrough

The changes update the remoteControl function in mac-player.sh to handle the "back" command differently for Music and Spotify apps, adjust the default and checking logic for the REMOTE_ACCESS option, and refine the cache file update logic. Unbinding for unsupported apps was removed.

Changes

Files Change Summary
scripts/mac-player.sh Refactored "back" command logic in remoteControl, changed REMOTE_ACCESS handling, improved cache update, and removed key unbinding for unsupported apps.

Possibly related PRs

  • Mac player #343: Introduces and documents the initial implementation of mac-player.sh, which is directly refined by the current changes.

Suggested reviewers

  • ethancedwards8
✨ 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: 1

🧹 Nitpick comments (1)
scripts/mac-player.sh (1)

202-202: Minor: treat option as boolean, not string

Storing the default as the string "false" then comparing with "true" works but is fragile (case-sensitivity, typos, non-bool values). Consider normalising the option:

REMOTE_ACCESS=$(get_tmux_option "@dracula-mac-player-remote" "false")
[[ ${REMOTE_ACCESS,,} == true ]]

This lowers the risk of mis-configuration.

📜 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 40ce9b7.

📒 Files selected for processing (1)
  • scripts/mac-player.sh (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
scripts/mac-player.sh (1)
scripts/utils.sh (1)
  • get_tmux_option (3-12)
🔇 Additional comments (2)
scripts/mac-player.sh (2)

210-218: Good move: remote-control options now loaded only when needed

Pulling the key-binding options inside the REMOTE_ACCESS guard avoids unnecessary look-ups and keeps the variable scope tight.


221-225: Cache update is now single-pass – nice

Storing trackStatus once and slicing the cached value eliminates the double command-execution and removes an extra subshell. This is a simple but valuable optimisation.

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.

1 participant