Fix previewDocs on Linux when using IntelliJ
#5
Conversation
This file contains 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
|
macOS was already fixed with #1, so be careful to not break macOS support again |
|
Yep, I've intentionally left the macOS commands the same as #1. I don't believe that running the new Linux ones would cause an issue, but as I'm unable to test macOS, I don't know that for sure. |
Su5eD
approved these changes
Feb 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, when
previewDocsis run through IntelliJ on Linux, it does not inherit custom paths from.bashrc. This becomes important when dealing with Node, which when installed through itsnvminstaller is not installed on the default path. This patch, based off this article, makes bash interactive, and fixes the path issues.I've intentionally opted to leave macOS alone, as I'm not aware enough of how its version of bash differs to know if this patch is required.
I'm hoping this also fixes #2, but I've switched to a
.debversion of IntelliJ at this point and haven't tested it.