Skip to content

Commit b364abc

Browse files
authored
Add debug instructions for VS Code Ionide extension (#27)
1 parent e4a39fa commit b364abc

File tree

2 files changed

+14
-0
lines changed

2 files changed

+14
-0
lines changed

content/Editors/Code/getting_started.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,3 +30,17 @@ Ionide plugins are activated when:
3030
* Opened workspace contains any `.fsproj`, `.fs`, or `.fsx` file
3131

3232
* New `.fsproj`, `.fs`, or `.fsx` file is created in workspace that was not containing those files before.
33+
34+
### Debug plugin activation
35+
36+
Sometimes, Ionide will not start working properly after its installation due to some local misconfiguration. For example, if its process reaches the configured user limit on the number of inotify instances.
37+
38+
Then, in order to better understand what is happening, you can check the Ionide logs at the VS Code program:
39+
40+
<img src="/static/images/debug-vs-code-logs.png" />
41+
42+
1. Click at the "View" button;
43+
2. Then, click at the "Output" and assert that the OUTPUT terminal will open;
44+
3. Finally, select the "Ionide" element at the drop down list.
45+
46+
There you can find all the logs related to this extension.
249 KB
Loading

0 commit comments

Comments
 (0)