Skip to content

Fix default Haskell VSCode extension settings in GitHub Codespace #146

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

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Fix default Haskell VSCode extension settings in GitHub Codespace #146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,12 +29,15 @@ source $(grep -m 1 -e '-env.sh$' store-paths.txt)
EOF

# This enforce those settings in DevContainer whatever "Settings Sync" user preferences ...
RUN bash -ic 'source $HOME/.bashrc && mkdir -p $HOME/.vscode-server/data/Machine/ && \
echo -e "{\n\
\"haskell.manageHLS\": \"PATH\",\n\
\"haskell.serverEnvironment\": { \"PATH\": \"$PATH\" },\n\
\"haskell.serverExecutablePath\": \"$(which haskell-language-server)\"\n\
}" > $HOME/.vscode-server/data/Machine/settings.json'
# ... VSCode DevContainer and GitHub Codespace does not look for the same settings file ><'
RUN mkdir -p $HOME/.vscode-server/data/Machine/ \
&& mkdir -p $HOME/.vscode-remote/data/Machine/ \
&& bash -ic 'echo -e "{\n \
\"haskell.manageHLS\": \"PATH\",\n \
\"haskell.serverEnvironment\": { \"PATH\": \"$PATH\" },\n \
\"haskell.serverExecutablePath\": \"$(which haskell-language-server)\"\n \
}" > $HOME/.vscode-server/data/Machine/settings.json' \
&& cp $HOME/.vscode-server/data/Machine/settings.json $HOME/.vscode-remote/data/Machine/settings.json

# FIXME: Consider moving this script into a Nix `writeShellApplication` trivial builder within the closure ...
# ... but that means I should figure it out how to pass to it $COMPILER_NIX_NAME as input?
Expand Down