[GH-ISSUE #80] Overriding default file grammars automatically #64

New issue

Open

opened 2026-05-05 15:00:55 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 15:00:55 -06:00

Owner

Originally created by @jacobmischka on GitHub (Apr 5, 2016).
Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/80

Currently, when I install meteor-api it overrides the default grammars for .js and .cson and other general filetypes. This is not correct behavior as mentioned in the docs, I did not manually disable the language-javascript package.

I'd much rather have to manually select the Meteor syntax when working in meteor than deselect it when I'm not.

Originally created by @jacobmischka on GitHub (Apr 5, 2016). Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/80 Currently, when I install meteor-api it overrides the default grammars for `.js` and `.cson` and other general filetypes. This is not correct behavior as mentioned in the docs, I did not manually disable the language-javascript package. I'd much rather have to manually select the Meteor syntax when working in meteor than deselect it when I'm not.

gitea-mirror commented

2026-05-05 15:00:58 -06:00

Author

Owner

@LeNiglo commented on GitHub (Dec 20, 2016):

Months later, it's still the case.
Any chance we get an update on this ?

@LeNiglo commented on GitHub (Dec 20, 2016): Months later, it's still the case. Any chance we get an update on this ?

gitea-mirror commented

2026-05-05 15:01:01 -06:00

Author

Owner

@awatson1978 commented on GitHub (Dec 20, 2016):

Hi there. The Atom Package Manager account is borked. I've logged requests for someone to reset it, but it may be easier to create a new package. Not much I can do about it.

@awatson1978 commented on GitHub (Dec 20, 2016): Hi there. The Atom Package Manager account is borked. I've logged requests for someone to reset it, but it may be easier to create a new package. Not much I can do about it.

gitea-mirror commented

2026-05-05 15:01:03 -06:00

Author

Owner

@jacobmischka commented on GitHub (Dec 20, 2016):

I ended up just uninstalling this package, but I have since run into this problem with some other packages.

For the other packages, I ended up working around the issue using the core.customFileTypes setting in config.cson

Unfortunately, meteor-api doesn't set a custom scope (source.js.meteor, for example), and instead uses the standard source.js. Because of this I'm not sure if you'll be able to override it.

This would work if the scope were set correctly, but you can try it anyway:

customFileTypes:
  "source.js": [
    "js"
]

@jacobmischka commented on GitHub (Dec 20, 2016): I ended up just uninstalling this package, but I have since run into this problem with some other packages. For the other packages, I ended up working around the issue using the [`core.customFileTypes` setting in `config.cson`](http://flight-manual.atom.io/using-atom/sections/basic-customization/#_customizing_language_recognition) Unfortunately, `meteor-api` doesn't set a custom scope (`source.js.meteor`, for example), and instead uses the standard `source.js`. Because of this I'm not sure if you'll be able to override it. This would work if the scope were set correctly, but you can try it anyway: ``` customFileTypes: "source.js": [ "js" ] ```

gitea-mirror commented

2026-05-05 15:01:04 -06:00

Author

Owner

@hayk94 commented on GitHub (Jan 27, 2017):

Any fixes or workarounds yet?

@hayk94 commented on GitHub (Jan 27, 2017): Any fixes or workarounds yet?

gitea-mirror commented

2026-05-05 15:01:05 -06:00

Author

Owner

@jacobmischka commented on GitHub (Jan 27, 2017):

You can fork this package, fix the scope like I mentioned then use the workaround I mentioned, and then install it with am via git.

@jacobmischka commented on GitHub (Jan 27, 2017): You can fork this package, fix the scope like I mentioned then use the workaround I mentioned, and then install it with am via git.