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
Run command on save feature #212029
Comments
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
This is in fact surprisingly difficult to do yourself.
{
"filewatcher.commands": [
{
"match": "\\.ts*",
"isAsync": true,
"cmd": "echo '${file} file content Changed'",
"event": "onFileChange"
}
]
}
inotifywait -e close_write,moved_to,create -m . |
while read -r directory events filename; do
if [ "$filename" = "myfile.py" ]; then
./myfile.py
fi
done
|
I would recommend making this a standard is possible, by allowing global options in the global |
The ability to run custom commands when you save specific file extensions in VSCode. Can be used to act as a "watch" feature when working with code to run bundlers when the user saves their code.
These commands that can be executed when a file is saved, can be done in the
.vscode/settings.json
file or in the globalsettings.json
file. An indicator will be in the bottom tool bar which will indicate when a command is being executed and when the command has finished executing for builds that may take a few seconds.EDIT:
I would recommend making this a standard is possible, by allowing global options in the global
settings.json
file and instead of having local setting in the.vscode/settings.json
file to have local settings in a file namedexecuteonsave.json
or something like that which other IDEs can integrate the standard of looking for aexecuteonsave.json
file and using it to know what commands to execute on save.The text was updated successfully, but these errors were encountered: