-
Notifications
You must be signed in to change notification settings - Fork 11
fix(shell-history): fix broken fish config script #22
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.
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
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
f41df53
fix(shell-history): fix fish sytax and ensure creating the sym link
eitsupi d6f4cf1
ci: test fish config
eitsupi 0b2a4be
ci: ensure run tests on PRs
eitsupi 1900ea7
test(shell-history): use the latest fish feature
eitsupi 4d98d3a
ci: use test.yaml from the latest feature-starter template
eitsupi 32564ac
test: fix test for fish
eitsupi e7c7a84
test: fix test name
eitsupi 7ef02f3
chore(shell-history): bump version
eitsupi d94314d
refactor(shell-history): use single quote
eitsupi b5cea4b
test(shell-history): more tests for fish
eitsupi 3016992
ci: remove failing test for now
eitsupi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,4 +2,10 @@ | |
|
|
||
| set -e | ||
|
|
||
| ./_default.sh | ||
| # Optional: Import test library bundled with the devcontainer CLI | ||
| source dev-container-features-test-lib | ||
|
|
||
| # Feature-specific tests | ||
| check "check fish config script validity" fish -c "source $HOME/.config/fish/config.fish" | ||
| check "check fish config script content" bash -c "cat $HOME/.config/fish/config.fish | grep -q 'XDG_DATA_HOME'" | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have added a test. I believe this test confirms that |
||
| check "cache dir permission" bash -c "test -w /dc/shellhistory" | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this work for you without the escaping?
I had to add the escaping back in for the bash history as otherwise the
$XDG_DATA_HOMEenv var is evaluated at the point thatoncreate.shruns and that wasn't set Escaping it ensured that it was evaluated when the.bashrcwas run.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your review.
IIUC, replacing
EOFto"EOF"allows us to use$without escaping here.https://en.wikipedia.org/wiki/Here_document
But from this Wikipedia page, perhaps single quoted
'EOF'might be better?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah - I'll file that under Things I Learned 😄
In terms of single vs double quoting, I think I prefer single as the article suggests