Skip to content

fix: use absolute path for wtp initialization to avoid PATH issues #57

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.

Sign up for GitHub

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

Jump to bottom
Merged
lox merged 1 commit into from
Oct 8, 2025
Merged

fix: use absolute path for wtp initialization to avoid PATH issues #57

lox merged 1 commit into from
Oct 8, 2025

Conversation

@lox
Copy link
Owner

@lox lox commented Oct 8, 2025 •
edited
Loading

Summary

  • Use absolute path $HOME/bin/wtp to avoid PATH resolution issues during shell reload
  • Add fallback to command -v wtp for robustness
  • Suppress stderr to avoid noise during shell initialization

Test plan

  • Verify wtp hooks work correctly after shell reload
  • Confirm no error messages during shell initialization
  • Test both with wtp in $HOME/bin and in PATH

@lox
fix: use absolute path for wtp initialization to avoid PATH issues
3d847d9 
During shell reload, the PATH might not be fully initialized when wtp
hooks are evaluated. Use $HOME/bin/wtp directly with a fallback to
command -v for more reliable initialization.
@lox lox merged commit 220c5fa into main Oct 8, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@lox