Mixing
Atom Editor Syntax Highlighting for ini files as Java Properties
I am using Atom 1.33.0 on MacOS X 10.13 High Sierra
To configure atom to recognize files with the extension ".ini" as Java Properties and apply the appropriate syntax highlighter I checked the following links:
- GitHub Atom: How to apply a particular syntax highlighting to some files based on name
- https://discuss.atom.io/t/how-do-i-make-atom-recognize-a-file-with-extension-x-as-language-y/26539
- https://flight-manual.atom.io/using-atom/sections/basic-customization/#finding-a-languages-scope-name
- https://stackoverflow.com/a/51321435/6204861
- https://discuss.atom.io/t/using-customfiletypes-to-change-the-language-for-html/40230
and assumed that the following config.cson would work:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.Java Properties': [
'ini'
]
...
unfortunately this does not have the desired effect.
To find the correct name i opened an example Java Properties ".ini" file as "Plain Text". Then I changed the syntax highlighting manually to "Java Properties" by clicking in the bottom right corner. Then I pressed Alt-CMD-P which showed:
So "source.java-properties" should be the correct name.
I modified config.cson accordingly to:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.java-properties': [
'ini'
]
And still it does not work.
What needs to be changed to make it work?
syntax-highlighting atom-editor
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
add a comment |
I am using Atom 1.33.0 on MacOS X 10.13 High Sierra
To configure atom to recognize files with the extension ".ini" as Java Properties and apply the appropriate syntax highlighter I checked the following links:
- GitHub Atom: How to apply a particular syntax highlighting to some files based on name
- https://discuss.atom.io/t/how-do-i-make-atom-recognize-a-file-with-extension-x-as-language-y/26539
- https://flight-manual.atom.io/using-atom/sections/basic-customization/#finding-a-languages-scope-name
- https://stackoverflow.com/a/51321435/6204861
- https://discuss.atom.io/t/using-customfiletypes-to-change-the-language-for-html/40230
and assumed that the following config.cson would work:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.Java Properties': [
'ini'
]
...
unfortunately this does not have the desired effect.
To find the correct name i opened an example Java Properties ".ini" file as "Plain Text". Then I changed the syntax highlighting manually to "Java Properties" by clicking in the bottom right corner. Then I pressed Alt-CMD-P which showed:
So "source.java-properties" should be the correct name.
I modified config.cson accordingly to:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.java-properties': [
'ini'
]
And still it does not work.
What needs to be changed to make it work?
syntax-highlighting atom-editor
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
add a comment |
I am using Atom 1.33.0 on MacOS X 10.13 High Sierra
To configure atom to recognize files with the extension ".ini" as Java Properties and apply the appropriate syntax highlighter I checked the following links:
- GitHub Atom: How to apply a particular syntax highlighting to some files based on name
- https://discuss.atom.io/t/how-do-i-make-atom-recognize-a-file-with-extension-x-as-language-y/26539
- https://flight-manual.atom.io/using-atom/sections/basic-customization/#finding-a-languages-scope-name
- https://stackoverflow.com/a/51321435/6204861
- https://discuss.atom.io/t/using-customfiletypes-to-change-the-language-for-html/40230
and assumed that the following config.cson would work:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.Java Properties': [
'ini'
]
...
unfortunately this does not have the desired effect.
To find the correct name i opened an example Java Properties ".ini" file as "Plain Text". Then I changed the syntax highlighting manually to "Java Properties" by clicking in the bottom right corner. Then I pressed Alt-CMD-P which showed:
So "source.java-properties" should be the correct name.
I modified config.cson accordingly to:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.java-properties': [
'ini'
]
And still it does not work.
What needs to be changed to make it work?
syntax-highlighting atom-editor
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
I am using Atom 1.33.0 on MacOS X 10.13 High Sierra
To configure atom to recognize files with the extension ".ini" as Java Properties and apply the appropriate syntax highlighter I checked the following links:
- GitHub Atom: How to apply a particular syntax highlighting to some files based on name
- https://discuss.atom.io/t/how-do-i-make-atom-recognize-a-file-with-extension-x-as-language-y/26539
- https://flight-manual.atom.io/using-atom/sections/basic-customization/#finding-a-languages-scope-name
- https://stackoverflow.com/a/51321435/6204861
- https://discuss.atom.io/t/using-customfiletypes-to-change-the-language-for-html/40230
and assumed that the following config.cson would work:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.Java Properties': [
'ini'
]
...
unfortunately this does not have the desired effect.
To find the correct name i opened an example Java Properties ".ini" file as "Plain Text". Then I changed the syntax highlighting manually to "Java Properties" by clicking in the bottom right corner. Then I pressed Alt-CMD-P which showed:
So "source.java-properties" should be the correct name.
I modified config.cson accordingly to:
"*":
core:
telemetryConsent: "no"
themes: [
"atom-light-ui"
"atom-light-syntax"
]
customFileTypes:
'source.java-properties': [
'ini'
]
And still it does not work.
What needs to be changed to make it work?
syntax-highlighting atom-editor
syntax-highlighting atom-editor
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
edited Jan 1 at 15:17
Wolfgang Fahl
6,674644100
6,674644100
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
asked Jan 1 at 11:59
Maria FahlMaria Fahl
516
516
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
the coffeescript parser seems to be very picky about details
The following config.cson works:
"*":
core:
customFileTypes:
"source.java-properties": [
"ini"
]
disabledPackages: [
"welcome"
]
...
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53995246%2fatom-editor-syntax-highlighting-for-ini-files-as-java-properties%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
the coffeescript parser seems to be very picky about details
The following config.cson works:
"*":
core:
customFileTypes:
"source.java-properties": [
"ini"
]
disabledPackages: [
"welcome"
]
...
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
add a comment |
the coffeescript parser seems to be very picky about details
The following config.cson works:
"*":
core:
customFileTypes:
"source.java-properties": [
"ini"
]
disabledPackages: [
"welcome"
]
...
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
add a comment |
the coffeescript parser seems to be very picky about details
The following config.cson works:
"*":
core:
customFileTypes:
"source.java-properties": [
"ini"
]
disabledPackages: [
"welcome"
]
...
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
the coffeescript parser seems to be very picky about details
The following config.cson works:
"*":
core:
customFileTypes:
"source.java-properties": [
"ini"
]
disabledPackages: [
"welcome"
]
...
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
answered Jan 1 at 15:30
Maria FahlMaria Fahl
516
516
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53995246%2fatom-editor-syntax-highlighting-for-ini-files-as-java-properties%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
