-
-
Notifications
You must be signed in to change notification settings - Fork 489
Closed
Assignees
@Wezz19
Description
Describe the problem
- No splashscreen at start
- Language server fails to start
- The text in the editor has no colors (probably caused by the language server)
The IDE is otherwise working. Verify, upload and serial monitor works normally.
To reproduce
Place a '#' in the IDE folder name and start the IDE.
Expected behavior
If '#' in the IDE folder name can't be supported in Windows due to limited support in other OS's then a notification to the user should make it clear that the IDE folder name contains an unsupported symbol.
Otherwise since the IDE seems to be running normally except for the language server then maybe it can be fixed to support '#' symbols in windows at least.
Arduino IDE version
nightly-20220628
Operating system
Windows
Operating system version
10
Additional context
2022年06月28日 11:53:12 root INFO [d044d6a1-4348-4d71-813b-f0efe4e7ed33] Start of 0 plugins: 203.1 ms [Finished 3.714 s after frontend start]
2022年06月28日 11:53:12 root INFO Starting language server: arduino:avr:uno
2022年06月28日 11:53:12 root INFO Failed to start language server for arduino:avr:uno
2022年06月28日 11:53:12 root INFO Starting language server: arduino:avr:uno
2022年06月28日 11:53:12 root INFO Failed to start language server for arduino:avr:uno
2022年06月28日 11:53:12 root INFO Starting language server: arduino:avr:uno
2022年06月28日 11:53:12 root INFO Failed to start language server for arduino:avr:uno
2022年06月28日 11:53:12 root INFO Starting language server: arduino:avr:uno
2022年06月28日 11:53:12 root INFO Failed to start language server for arduino:avr:uno
2022年06月28日 11:53:12 root INFO Starting language server: arduino:avr:uno
2022年06月28日 11:53:12 root INFO Failed to start language server for arduino:avr:uno
2022年06月28日 11:53:12 root INFO Starting language server: arduino:avr:uno
2022年06月28日 11:53:12 root INFO Failed to start language server for arduino:avr:uno
2022年06月28日 11:53:13 root INFO Frontend application start: 2637.1 ms [Finished 6.808 s after backend start]
Issue checklist
- I searched for previous reports in the issue tracker
- I verified the problem still occurs when using the latest nightly build
- My report contains all necessary details