Skip to content

Use full bun and pulse paths in LLM tmux binding#11

Merged
fetep merged 1 commit intomainfrom
petef/dev
Mar 18, 2026
Merged

Use full bun and pulse paths in LLM tmux binding#11
fetep merged 1 commit intomainfrom
petef/dev

Conversation

@fetep
Copy link
Copy Markdown
Owner

@fetep fetep commented Mar 18, 2026

Changes

  • docs: use full bun and pulse paths in LLM tmux binding

Copilot AI review requested due to automatic review settings March 18, 2026 23:30
@fetep fetep changed the title Improve README install docs with LLM guide and full paths Use full bun and pulse paths in LLM tmux binding Mar 18, 2026
@fetep fetep merged commit 298657d into main Mar 18, 2026
7 checks passed
@fetep fetep deleted the petef/dev branch March 18, 2026 23:32
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the README’s LLM-assisted installation workflow to make tmux integration more reliable by avoiding PATH-dependent invocation and clarifying how to derive absolute executable paths.

Changes:

  • Add commands/instructions to determine absolute paths for bun and the globally-installed pulse.
  • Update the suggested tmux display-popup binding to invoke pulse via an explicit bun path.
  • Adjust the verification step wording to encourage using full paths.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

Comment on lines +60 to +63
After installation, get the full paths to both bun and pulse:
```bash
which bun
echo "$(bun pm bin -g)/pulse"
### Step 5: Verify and finish

Run `pulse --help` to confirm the binary works.
Run the full path to pulse with --help to confirm the binary works.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants