Search Issue Tracker
Not Reproducible
Votes
2
Found in
2017.3.0p2
Issue ID
992180
Regression
No
[Linux Editor] External editor arguments field is missing for Visual Studio Code
Steps to reproduce:
1. Install Visual Studio Code for Ubuntu (https://code.visualstudio.com/download)
2. Create an empty project in Unity
3. Set Visual Studio code as the default editor under Edit->Preferences->External Editors
4. Notice that the field for External Script Editor Arguments does not appear
Note: It is stated in https://code.visualstudio.com/docs/other/unity that "Unity has built-in support for opening scripts in Visual Studio Code as an external script editor on Windows and macOS. Unity will detect when Visual Studio Code is selected as an external script editor and pass the correct arguments to it when opening scripts from Unity", however it does not on Linux and users are not allowed to enter the correct arguments themselves.
Reproduced on: 2017.3.0b1, 2017.3.0f1, 2017.3.0p2
-
howzitcal
May 19, 2019 03:25
Hey Guys, using Unity 2018.2.7f1 on Ubuntu 18.04.
Seems that if you select the monodevelop binary from /usr/bin/ it removes that ability for you to add the file arg.
However I just selected Atom as my default editor and the file args field has re appeared...
So short/long term solution is to use VSCode or Atom instead of MonoDevelop as the default editor of C# scripts.
-
Sneirox
Jan 20, 2019 14:36
The same bug on Unity 2018.3.0f2
-
Sneirox
Jan 20, 2019 14:35
The same bug on Unity 2018.3.0f2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The USS cursor style property is not applied when it is set for the root VisualElement
- [Player Settings] [Common] [Optimization] - Setting 'Preload Assets' throws parser error
- Editor crashes on physx::shdfnd::internal::HashBase or freezes when instantiating a lot of GameObjects
- Audio Source stops playing when moved to a scene with LocalPhysicsMode.Physics2D Parameter
- "NullReferenceException: Object reference not set to an instance of an object" error is thrown in the Play Mode when the project is reopened with a Prefab GameObject selected in the SerializedField
Resolution Note:
Appears to be working well with VSCode in the latest 19.1. Missing args in settings window is by design.