Skip to content

[Bug]: Additional Environment Variables or cmd:initscript do not work in WSL #2177

Open
@dmiric

Description

@dmiric

Current Behavior

Additional Environment Variables don't seem to work in WSL and almost nothing else does from the connection configuration. I'm not 100% sure that I'm not doing something wrong.

I also wanted to setup connection to like this:
{
"wsl://Ubuntu": {
"conn:wshenabled": true,
"cmd:initscript.zsh": "(echo '--- Wave Init Script Starting ---'; pwd; cd ~/projects || { echo 'ERROR: cd failed!'; exit 1; }; echo 'Current directory after cd:'; pwd; source ~/.zshrc; echo '--- Wave Init Script Finished ---') &> /tmp/wave_init_debug_output.log"
}
}

cmd:initscript.zsh seems to not be doing nothing, I tried cmd:initscript also nothing.

Expected Behavior

I think everything that works for any other connection should work for WSL connection.

Steps To Reproduce

Just normal WSL and Waveterm installation

Wave Version

v0.11.3

Platform

Windows

OS Version/Distribution

11

Architecture

arm64

Anything else?

No response

Questionnaire

  • I'm interested in fixing this myself but don't know where to start
  • I would like to fix and I have a solution
  • I don't have time to fix this right now, but maybe later

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageNeeds triage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions