devenv: add devenv.debug option #556
Merged
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
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 there are problems it is hard to reproduce and hard to find out which parts of
enterShellare at fault. To get more information about what is going on I thought it was nice to have a debug option in devenv that enables debugging in bash when running the shellHook/enterShell scripts.This was done in response to #555, which seemed like an issue that was hard to reproduce.
This allows people to add
devenv.debug = true;to their configuration and it would show all lines that were executed by bash.I thought about adding a test, but I couldn't find a good/nice way to do so. Suggestions are welcome!