add CWD in server status output #36
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Forwarding mvoidex#1 to the upstream.
README mentions that filenames are resolved relative to the server's CWD (current working directory) — rather than to the client's.
While it's technically possible to intrusively determine working path of a foreign process (with tools like
readlink /proc/$PID/cwd, orprocexp.exeon Windows) — these methods are rarely userfriendly and mostly inconvenient for regular use (though excellent for troubleshooting/debug).This addition can be very useful to simplify hdevtools setup and plugin integration, especially on Windows.