vscode-tasks

How do i automatically clear the terminal in VSCode before execution of script? [duplicate]

回眸只為那壹抹淺笑 提交于 2020-07-23 06:45:33
问题 This question already has answers here : How to clear the interpreter console? (36 answers) Closed 17 hours ago . I am currently using VS Code to learn Python . So i have to run scripts like 10-15 times a minute , just doing small edits and learning all things. I am running the scripts in integrated terminal of VS code So apparently the terminal gets horribly cluttered and i have to always clear the terminal manually by running clear , I want the terminal to automatically get cleared every

How do I automatically clear VS Code terminal when starting a build?

我与影子孤独终老i 提交于 2020-06-07 13:41:07
问题 I press Ctrl + Shift + B to start a build in Visual Studio Code (it's configured to just run GNU Make), and the build tool output is written to the Terminal window. However, it's appended to the output from the previous build, which is confusing. How do I configure VS Code to clear the terminal window before starting a new build? 回答1: November 2018 Update As of this commit (and a few subsequent follow-ups), you can now add a clear presentation option to your task to have it clear the terminal

How do I automatically clear VS Code terminal when starting a build?

北城余情 提交于 2020-06-07 13:40:32
问题 I press Ctrl + Shift + B to start a build in Visual Studio Code (it's configured to just run GNU Make), and the build tool output is written to the Terminal window. However, it's appended to the output from the previous build, which is confusing. How do I configure VS Code to clear the terminal window before starting a new build? 回答1: November 2018 Update As of this commit (and a few subsequent follow-ups), you can now add a clear presentation option to your task to have it clear the terminal

How do I specify the include path when I build a program in VSCode?

别说谁变了你拦得住时间么 提交于 2020-05-14 10:26:41
问题 Let's say this is my project. file structure: project_root |-- inc | |-- header.h |-- src | |-- helpers.c | |-- main.c header.h #ifndef HEADER_H # define HEADER_H void func(void); #endif helpers.c void func() { /* do something */ } main.c #include "header.h" int main(void) { func(); return (0); } c_cpp_properties.json { "configurations": [ { "name": "Mac", "includePath": [ "${workspaceFolder}/inc", ], "defines": [], "macFrameworkPath": [ "/System/Library/Frameworks", "/Library/Frameworks" ],

How do I specify the include path when I build a program in VSCode?

我与影子孤独终老i 提交于 2020-05-14 10:25:49
问题 Let's say this is my project. file structure: project_root |-- inc | |-- header.h |-- src | |-- helpers.c | |-- main.c header.h #ifndef HEADER_H # define HEADER_H void func(void); #endif helpers.c void func() { /* do something */ } main.c #include "header.h" int main(void) { func(); return (0); } c_cpp_properties.json { "configurations": [ { "name": "Mac", "includePath": [ "${workspaceFolder}/inc", ], "defines": [], "macFrameworkPath": [ "/System/Library/Frameworks", "/Library/Frameworks" ],

VSCode TypeScript problemMatcher `$tsc-watch` not watching

☆樱花仙子☆ 提交于 2020-05-12 02:56:52
问题 I'm trying to avoid having to use watch: true in a tsconfig.json configuration. Through VSCode's tasks I'm using the base problem matcher $tsc-watch but it's not launching tsc in watch mode when building. I'm adding gulp support and I see there is gulp-watch but I'd like to understand why $tsc-watch isn't working as I believe it should. 回答1: I figured this out by looking at the typescript extension's taskProvider.js . In order for tsc-watch to function the task needed option: "watch" to be

Is there a VS Code shortcut for creating a new file from selected or clipboard code?

蹲街弑〆低调 提交于 2020-04-16 04:16:36
问题 I work with large html files that I would like to fragment into separate files. The process of doing this is quite tedious as it requires copying the code, creating a new file, pasting it in the new file, and then selecting a folder and a new name to save it under. Is there a built-in shortcut, macro or extension for VS Code for making this easier? 回答1: Here is a macro which does what you want. I am using the macro extension multi-command but there are others. In settings.json: "multiCommand

How to Setup VS Code For C++ 14 /C ++17

大憨熊 提交于 2020-04-14 07:28:46
问题 I tried to run a .cpp file from workspace but giving me this error about not adding c++11/higher flags but I have added them in task.json Error [Running] cd "c:\Users\Nuhash\Desktop\test\" && g++ main.cpp -o main && "c:\Users\Nuhash\Desktop\test\"main main.cpp:8:1: error: expected unqualified-id before 'using' using ordered_set = tree<T, null_type, less<T>, rb_tree_tag, tree_order_statistics_node_update>; ^ main.cpp:10:1: error: expected unqualified-id before 'using' using ordered_set_rev =

Create multiple terminals and run commands in VSCode

安稳与你 提交于 2020-04-13 14:52:31
问题 I'm on a Mac 💻. I'm trying to explore a way to create 4 Terminals as soon as I dbl-clicked on my workspace file. I've tried to get one working, but I seem stuck { "folders": [ { "path": "/Users/bheng/Sites/laravel/project" } ], "settings": { "workbench.action.terminal.focus": true, "terminal.integrated.shell.osx": "ls", "terminal.integrated.shellArgs.osx": [ "ls -lrt" ] }, "extensions": {} } My goal is to open 4 Terminals Terminal1 : run 'npm run watch' Terminal2 : run 'ls -lrt' Terminal3 :