You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/guide/choosing-an-editor.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ If you do choose to [try Visual Studio Code](https://code.visualstudio.com/), le
16
16
17
17
After you install Visual Studio Code, you can open projects using the editor's `File` → `Open` menu option, but there's an alternative option that works far better for command-line-based projects like NativeScript: the `code` command.
18
18
19
-
The `code` command runs in your command-line or terminal, and it works just like the `ns` command does for NativeScript apps. Visual Studio Code installs the `code` command by default on Windows on Linux, but on macOS, there's [one manual step](https://code.visualstudio.com/docs/setup/mac) you must perform.
19
+
The `code` command runs in your command-line or terminal, and it works just like the `ns` command does for NativeScript apps. Visual Studio Code installs the `code` command by default on Windows and Linux, but on macOS, there's [one manual step](https://code.visualstudio.com/docs/setup/mac) you must perform.
20
20
21
-
Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of command to create a new NativeScript app and open it for editing.
21
+
Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of commands to create a new NativeScript app and open it for editing.
0 commit comments