-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught TypeError: atom.grammars.startIdForScope is not a function #1020
Comments
Hi. I get the same error message in Atom 1.24.0-beta3 x64 / Windows 10 Pro x64. I've also tried Atom 1.23.3 x64 / Windows 10 Pro x64... and I get different error. And package is omnisharp-atom 0.31.2 Either way, can't get OmniSharp icon turn green, and of course, intellisense etc doesn't work. However, with Sublime Text 3 I can get omnisharp working, however, I have no idea what the difference or similarities between Atom and Sublime Text omnisharp are... if there are any similarities or such. I'm pretty noob in anything coding, not even sure what .Net should be installed for omnisharp to work, I was going to try using atom as alternative IDE for Unity + C# use. |
Same on released production version 1.24 on Mac OS X: [Enter steps to reproduce:]
Atom: 1.24.0 x64 Stack TraceUncaught TypeError: atom.grammars.startIdForScope is not a function
Commands
Non-Core Packages
|
I'm not sure if this is related, but I have a similar issue in my own package and have started a discussion on atom.io to see if there's any support: |
I'm having the same issue. Steps to reproduce:
Atom: 1.24.0 x64 Stack TraceFailed to activate the omnisharp-atom package
Commands
Non-Core Packages
|
Im having the same issue, but i have Linux(Ubuntu), i have this problem since 2 weeks, and i was looking for solved this for all that time, this is what drop:
Atom: 1.24.0 x64 Stack TraceUncaught TypeError: atom.grammars.startIdForScope is not a function
Commands
Non-Core Packages
|
Same issue here
Atom: 1.24.0 x64 Stack TraceFailed to activate the omnisharp-atom package
Commands
Non-Core Packages
|
Not meaning to be rude, but just wondering if this project has been dropped in favour of https://github.com/OmniSharp/omnisharp-vscode, as there hasn't been a commit here in over 10 months, and issues don't seem to be getting addressed? I'd be possibly interested in helping move it from DNVM to DotNet CLI, which seems to be the cause of the latest build fail, but not if it's being deprecated. |
Simple solutionReplace 140 line of omnisharp-atom.js from: |
Didn't work for me. |
Didn't work for me neither :/ |
@koxu1996 's solution is really close The |
It seems to solve that problem, thanks for both of you! I have another error to start the package, though, which seems to be unrelated. I will open a new issue for that one. |
Thank you!! It worked for me! |
Can you post the updated solution? I'm having trouble understanding. |
@theslyprofessor I might be a little late, but I have gotten it to work by finding the file omnisharp-atom.js. It's located in the your-username/.atom/packages/omnisharp-atom/dist folder. If you don't find it there, try letting explorer search for omnisharp-atom.js in the whole drive, and it should find it ... Anyway, find it and open it in a text editor, then search for "var grammars = atom.grammars;". This will take you to line 140. Replace that whole line with "var grammars = atom.grammars.textmateRegistry || atom.grammars;". Then you shall move on to line 145, "atom.grammars.startIdForScope(grammar.scopeName);" and replace it with "grammars.startIdForScope(grammar.scopeName);". Then you save the file and relaunch Atom. |
@theslyprofessor is right but then if you have installed linder-ui-default it sends you and error like its something ilegal, u have to uninstall then it runs, but it someone knows how to avoid uninstall, please contact me thanks |
Steps to reproduce:
Atom: 1.24.0-beta1 x64
Electron: 1.6.15
OS: Microsoft Windows 10 Enterprise
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Uncaught TypeError: atom.grammars.startIdForScope is not a function
Non-Core Packages
The text was updated successfully, but these errors were encountered: