Skip to content

Conversation

@jparise
Copy link
Contributor

@jparise jparise commented Dec 24, 2025

Command-based shell detection has been extracted to its own function (detectShell), which is nicer for testing. It now uses argIterator to determine the command's executable, rather than the previous string operations, which allows us to handle command strings containing quotes and spaces.

Also, our shell-specific setup functions now use a consistent signature, which simplifies the calling code quite a bit.

@jparise jparise added this to the 1.3.0 milestone Dec 24, 2025
@jparise jparise requested a review from a team as a code owner December 24, 2025 17:49
@jparise
Copy link
Contributor Author

jparise commented Dec 24, 2025

#10035 will need a small update for this change (or vice-versa). I'll sort that out based on merge order.

Copy link
Contributor

@mitchellh mitchellh left a comment

Choose a reason for hiding this comment

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

Merged #10035 so please request me for re-review when ready. 😄

@jparise jparise force-pushed the shell-integration-setup branch from 5ececaa to 012cde0 Compare December 27, 2025 02:00
@jparise jparise requested a review from mitchellh December 27, 2025 02:01
@jparise
Copy link
Contributor Author

jparise commented Dec 27, 2025

Merged #10035 so please request me for re-review when ready. 😄

All set, thanks!

@jparise
Copy link
Contributor Author

jparise commented Dec 30, 2025

Merged #10035 so please request me for re-review when ready. 😄

All set, thanks!

@mitchellh everything look good?

@mitchellh
Copy link
Contributor

Sorry haven't had a chance to look yet. I'll try to do it this week before anything else causes conflicts. 😄

Command-based shell detection has been extracted to its own function
(detectShell), which is nicer for testing. It now uses argIterator to
determine the command's executable, rather than the previous string
operations, which allows us to handle command strings containing quotes
and spaces.

Also, our shell-specific setup functions now use a consistent signature,
which simplifies the calling code quite a bit.
@mitchellh mitchellh force-pushed the shell-integration-setup branch from 012cde0 to 795de79 Compare January 7, 2026 18:25
Copy link
Contributor

@mitchellh mitchellh left a comment

Choose a reason for hiding this comment

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

Just added type hints to the const. I prefer that.

@mitchellh mitchellh merged commit 9bddca8 into ghostty-org:main Jan 7, 2026
50 checks passed
@jparise jparise deleted the shell-integration-setup branch January 7, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants