Error when default shell is non POSIX
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
Start at the terminal-wakatime init entry point and trace how the shell is selected when invoked from Fish versus Bash; the issue identifies config.fish and bashrc as the affected files. Done means the generated bashrc line explicitly requests Bash and a Bash subshell no longer receives Fish configuration.
Written by the indexing model from the issue text.
Description
When running the script with Fish and letting it modify the config.fish and bashrc files it will write the respective terminal-wakatime init at the bottom of the files. The problem is when I use a bash as a subshell (Ran from fish) that command outputs the config of fish rather than bash, and, since fish is not posix it doesn't works.
It can be corrected by always specifying which shell you're using, i.e; terminal-wakatime init bash. But it should be made the default option for bash too (SInce it already specifies it when writing to config.fish).
- Dominant language
- Rust
- Stars
- 5
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100