VSCode

VSCode (Visual Studio Code) is one of the most widely used code editors. It is highly configurable, which leads to a great user experience, and provides support for almost any programming language via extensions. It also boasts a large number of features to help boost your productivity. Thus, I strongly recommend that you consider using VSCode if you haven't been using it already. VSCode is also available on the CSE lab machines, so if you've been using only gedit thus far, now is the time to upgrade! For coding in C, some extensions you should get are:

• C/C++, by Microsoft
• Remote - WSL, by Microsoft (for WSL users) - this extension enables you to access and edit files in the Linux side of the WSL file system.

You can learn more about these extensions on their respective pages in the Visual Studio Code Marketplace. You can also browse extensions within VSCode itself. Some extensions that you don't need, but I still recommend, are:

• Better Comments, by Aaron Bond
• TODO Highlight, by Wayou Liu - this extension lets you add your own highlighted keywords, such as BUG, NOTE, and IMPORTANT.

Let me know if you find any other useful extensions.

Setting up VSCode on CSE

The command to open a file in VSCode is very similar to the command to open a file in gedit - simply replace gedit with code.

$ code IntList.c timing.txt &
			

Unlike gedit, you can also open directories/folders in VSCode. This will cause a file explorer to appear on the left, and you can then choose which files you want to open.

$ code . &
			

If this is your first time using VSCode on CSE, then click on the extensions icon on the left toolbar and install the C/C++ extension. This will give you IntelliSense for C, which includes autocomplete, type checking and many other features.