Different colorisation for Json properties and values
Using N++ to quickly inspect Json, I have the following issue:
Everything is grey. Properties / Text Values.
But in N++ Style Configurator, there is no option for Value and Property Name. It's just String single quote or double quote.
Is there a language or configuration that will provide a more colorfull colorisation for Json ?
Exemple :
For the following Json:
{"description":{"title":"Contiguous U.S., Average Temperature","units":"Degrees Fahrenheit","base_period":"1901-2000"},"data":{"189512":{"value":"50.34","anomaly":"-1.68"},"189612":{"value":"51.99","anomaly":"-0.03"},"189712":{"value":"51.56","anomaly":"-0.46"}}}
N++ will give this representation:
Your eyes must look for the :
then roll back to read the property name. Especially on multiline data (indented and auto carriage return so you don't horizontal scroll into infinity).
While I expected that kind of result(Don't min the dark theme) from quicktype.io
notepad++
add a comment |
Using N++ to quickly inspect Json, I have the following issue:
Everything is grey. Properties / Text Values.
But in N++ Style Configurator, there is no option for Value and Property Name. It's just String single quote or double quote.
Is there a language or configuration that will provide a more colorfull colorisation for Json ?
Exemple :
For the following Json:
{"description":{"title":"Contiguous U.S., Average Temperature","units":"Degrees Fahrenheit","base_period":"1901-2000"},"data":{"189512":{"value":"50.34","anomaly":"-1.68"},"189612":{"value":"51.99","anomaly":"-0.03"},"189712":{"value":"51.56","anomaly":"-0.46"}}}
N++ will give this representation:
Your eyes must look for the :
then roll back to read the property name. Especially on multiline data (indented and auto carriage return so you don't horizontal scroll into infinity).
While I expected that kind of result(Don't min the dark theme) from quicktype.io
notepad++
An issue I don't have with Xml as the text pop out of the Tag.
– Drag and Drop
Jan 16 at 14:11
ClickLanguage
->J
->JSON
. It should auto apply the styles to your document
– Burgi
Jan 16 at 17:06
@Burgi, Well as I'm talking about the Style configurator, I thought it was obvious that the style was already selected. But it's my bad the last line can be read as "Is there a language that will provide colorisation for Json?." And the answer will be Json. Let me edit some picture to show you what i mean by more color and colorfull
– Drag and Drop
Jan 17 at 10:00
When I ask for other language it's because there were a time where colorisation from not related language gave better result on some block code. Lambda C# and Java come in mind. But that was in 2008.
– Drag and Drop
Jan 17 at 10:12
May I ask why the down vote? I know N++ is not Vim or an EDI. But simple parsing and highlight is not high evolution. Is the question not legitimate ("You don't have to do that. Copy past in your other editor that does proper higlight")? To basic - no research(Use the standard higtlight)?
– Drag and Drop
Jan 28 at 10:55
add a comment |
Using N++ to quickly inspect Json, I have the following issue:
Everything is grey. Properties / Text Values.
But in N++ Style Configurator, there is no option for Value and Property Name. It's just String single quote or double quote.
Is there a language or configuration that will provide a more colorfull colorisation for Json ?
Exemple :
For the following Json:
{"description":{"title":"Contiguous U.S., Average Temperature","units":"Degrees Fahrenheit","base_period":"1901-2000"},"data":{"189512":{"value":"50.34","anomaly":"-1.68"},"189612":{"value":"51.99","anomaly":"-0.03"},"189712":{"value":"51.56","anomaly":"-0.46"}}}
N++ will give this representation:
Your eyes must look for the :
then roll back to read the property name. Especially on multiline data (indented and auto carriage return so you don't horizontal scroll into infinity).
While I expected that kind of result(Don't min the dark theme) from quicktype.io
notepad++
Using N++ to quickly inspect Json, I have the following issue:
Everything is grey. Properties / Text Values.
But in N++ Style Configurator, there is no option for Value and Property Name. It's just String single quote or double quote.
Is there a language or configuration that will provide a more colorfull colorisation for Json ?
Exemple :
For the following Json:
{"description":{"title":"Contiguous U.S., Average Temperature","units":"Degrees Fahrenheit","base_period":"1901-2000"},"data":{"189512":{"value":"50.34","anomaly":"-1.68"},"189612":{"value":"51.99","anomaly":"-0.03"},"189712":{"value":"51.56","anomaly":"-0.46"}}}
N++ will give this representation:
Your eyes must look for the :
then roll back to read the property name. Especially on multiline data (indented and auto carriage return so you don't horizontal scroll into infinity).
While I expected that kind of result(Don't min the dark theme) from quicktype.io
notepad++
notepad++
edited Jan 17 at 10:04
Drag and Drop
asked Jan 16 at 14:03
Drag and DropDrag and Drop
3461310
3461310
An issue I don't have with Xml as the text pop out of the Tag.
– Drag and Drop
Jan 16 at 14:11
ClickLanguage
->J
->JSON
. It should auto apply the styles to your document
– Burgi
Jan 16 at 17:06
@Burgi, Well as I'm talking about the Style configurator, I thought it was obvious that the style was already selected. But it's my bad the last line can be read as "Is there a language that will provide colorisation for Json?." And the answer will be Json. Let me edit some picture to show you what i mean by more color and colorfull
– Drag and Drop
Jan 17 at 10:00
When I ask for other language it's because there were a time where colorisation from not related language gave better result on some block code. Lambda C# and Java come in mind. But that was in 2008.
– Drag and Drop
Jan 17 at 10:12
May I ask why the down vote? I know N++ is not Vim or an EDI. But simple parsing and highlight is not high evolution. Is the question not legitimate ("You don't have to do that. Copy past in your other editor that does proper higlight")? To basic - no research(Use the standard higtlight)?
– Drag and Drop
Jan 28 at 10:55
add a comment |
An issue I don't have with Xml as the text pop out of the Tag.
– Drag and Drop
Jan 16 at 14:11
ClickLanguage
->J
->JSON
. It should auto apply the styles to your document
– Burgi
Jan 16 at 17:06
@Burgi, Well as I'm talking about the Style configurator, I thought it was obvious that the style was already selected. But it's my bad the last line can be read as "Is there a language that will provide colorisation for Json?." And the answer will be Json. Let me edit some picture to show you what i mean by more color and colorfull
– Drag and Drop
Jan 17 at 10:00
When I ask for other language it's because there were a time where colorisation from not related language gave better result on some block code. Lambda C# and Java come in mind. But that was in 2008.
– Drag and Drop
Jan 17 at 10:12
May I ask why the down vote? I know N++ is not Vim or an EDI. But simple parsing and highlight is not high evolution. Is the question not legitimate ("You don't have to do that. Copy past in your other editor that does proper higlight")? To basic - no research(Use the standard higtlight)?
– Drag and Drop
Jan 28 at 10:55
An issue I don't have with Xml as the text pop out of the Tag.
– Drag and Drop
Jan 16 at 14:11
An issue I don't have with Xml as the text pop out of the Tag.
– Drag and Drop
Jan 16 at 14:11
Click
Language
-> J
-> JSON
. It should auto apply the styles to your document– Burgi
Jan 16 at 17:06
Click
Language
-> J
-> JSON
. It should auto apply the styles to your document– Burgi
Jan 16 at 17:06
@Burgi, Well as I'm talking about the Style configurator, I thought it was obvious that the style was already selected. But it's my bad the last line can be read as "Is there a language that will provide colorisation for Json?." And the answer will be Json. Let me edit some picture to show you what i mean by more color and colorfull
– Drag and Drop
Jan 17 at 10:00
@Burgi, Well as I'm talking about the Style configurator, I thought it was obvious that the style was already selected. But it's my bad the last line can be read as "Is there a language that will provide colorisation for Json?." And the answer will be Json. Let me edit some picture to show you what i mean by more color and colorfull
– Drag and Drop
Jan 17 at 10:00
When I ask for other language it's because there were a time where colorisation from not related language gave better result on some block code. Lambda C# and Java come in mind. But that was in 2008.
– Drag and Drop
Jan 17 at 10:12
When I ask for other language it's because there were a time where colorisation from not related language gave better result on some block code. Lambda C# and Java come in mind. But that was in 2008.
– Drag and Drop
Jan 17 at 10:12
May I ask why the down vote? I know N++ is not Vim or an EDI. But simple parsing and highlight is not high evolution. Is the question not legitimate ("You don't have to do that. Copy past in your other editor that does proper higlight")? To basic - no research(Use the standard higtlight)?
– Drag and Drop
Jan 28 at 10:55
May I ask why the down vote? I know N++ is not Vim or an EDI. But simple parsing and highlight is not high evolution. Is the question not legitimate ("You don't have to do that. Copy past in your other editor that does proper higlight")? To basic - no research(Use the standard higtlight)?
– Drag and Drop
Jan 28 at 10:55
add a comment |
1 Answer
1
active
oldest
votes
The Scintilla component used by Notepad++ is in charge of the lexers for syntax highlighting. Apparently, the designer of that lexer didn't decide to differentiate between property names and values, though it seems like a good idea. To make a suggestion for that improvement in the lexer, you'd have to go see if the most recent Scintilla JSON Lexer has already incorporated that change, and if not, put in a request with the Scintilla project. If the change is already there, or if Scintilla releases a new version with that fix for you, you would then have to ask Notepad++ developer to upgrade Scintilla to include that fix. (And the last time NPP upgraded it's Scintilla was from 3.34 to 3.56 -- about 4 years ago -- compared to the most-recent Scintilla 4.1.3)
Workaround #1: change the Style Configurator > JSON > Operator color to have something that stands out between the property and value -- maybe with a bright yellow background or something -- to make it easier for your eye to find the :
separators, at least...
Workaround #2: In the Community Forums, Claudia Frank had done some work on a PythonScript-based lexer which would allow user defined languages with regular expressions, rather than the simplistic UDL 2.1. My collection of links to her effort is at https://notepad-plus-plus.org/community/topic/16164/bug-javascript-multiline-character-not-understood-by-notepad/11. With some effort, you might be able to define the regex necessary to parse JSON in a way you like.
update: You might be able to get a UDL (User Defined Language) to do what you want. I came up with a quick one that will get the highlighting differences you described. As a nasty side effect, it breaks folding (so cannot collapse { ... }
pairs. (I tried setting the UDL folding options, but nested folds weren't working right, at least on my first attempt)
Language > Define Your Language...: Create New = JsonPropertyValues.- Operators & Delimiters
Operators 1 =, : " ' { }
, STYLER = set whatever colors you want for the punctuation
Delimiter 1 style = OPEN::
, Close =((EOL))
, STYLER = set the color you want the VALUE side to be; setNesting:
to allowOperators 1
Delimiter 2 style = OPEN:"
, Close ="
, STYLER = set the color for left-side (property) when in double-quotes, no nesting needed
Delimiter 3 style = OPEN:'
, Close ='
, STYLER = set the color for left-side (property) when in single-quotes, no nesting needed
You might want to set Nesting:
to include Numbers
on all of those STYLER entries above. And then go to the Comment & Number tab and define the STYLER to set the coloring for numbers as well.
You could set the Ext box to json
, if you want it to apply to all .JSON
files, or you could just manually apply Language > JsonPropertyValues to any JSON that you want to parse in this manner.
Anyway, this is a reasonable starting point, based on what you described; feel free to customize it or expand it beyond the features included.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1394957%2fdifferent-colorisation-for-json-properties-and-values%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 Scintilla component used by Notepad++ is in charge of the lexers for syntax highlighting. Apparently, the designer of that lexer didn't decide to differentiate between property names and values, though it seems like a good idea. To make a suggestion for that improvement in the lexer, you'd have to go see if the most recent Scintilla JSON Lexer has already incorporated that change, and if not, put in a request with the Scintilla project. If the change is already there, or if Scintilla releases a new version with that fix for you, you would then have to ask Notepad++ developer to upgrade Scintilla to include that fix. (And the last time NPP upgraded it's Scintilla was from 3.34 to 3.56 -- about 4 years ago -- compared to the most-recent Scintilla 4.1.3)
Workaround #1: change the Style Configurator > JSON > Operator color to have something that stands out between the property and value -- maybe with a bright yellow background or something -- to make it easier for your eye to find the :
separators, at least...
Workaround #2: In the Community Forums, Claudia Frank had done some work on a PythonScript-based lexer which would allow user defined languages with regular expressions, rather than the simplistic UDL 2.1. My collection of links to her effort is at https://notepad-plus-plus.org/community/topic/16164/bug-javascript-multiline-character-not-understood-by-notepad/11. With some effort, you might be able to define the regex necessary to parse JSON in a way you like.
update: You might be able to get a UDL (User Defined Language) to do what you want. I came up with a quick one that will get the highlighting differences you described. As a nasty side effect, it breaks folding (so cannot collapse { ... }
pairs. (I tried setting the UDL folding options, but nested folds weren't working right, at least on my first attempt)
Language > Define Your Language...: Create New = JsonPropertyValues.- Operators & Delimiters
Operators 1 =, : " ' { }
, STYLER = set whatever colors you want for the punctuation
Delimiter 1 style = OPEN::
, Close =((EOL))
, STYLER = set the color you want the VALUE side to be; setNesting:
to allowOperators 1
Delimiter 2 style = OPEN:"
, Close ="
, STYLER = set the color for left-side (property) when in double-quotes, no nesting needed
Delimiter 3 style = OPEN:'
, Close ='
, STYLER = set the color for left-side (property) when in single-quotes, no nesting needed
You might want to set Nesting:
to include Numbers
on all of those STYLER entries above. And then go to the Comment & Number tab and define the STYLER to set the coloring for numbers as well.
You could set the Ext box to json
, if you want it to apply to all .JSON
files, or you could just manually apply Language > JsonPropertyValues to any JSON that you want to parse in this manner.
Anyway, this is a reasonable starting point, based on what you described; feel free to customize it or expand it beyond the features included.
add a comment |
The Scintilla component used by Notepad++ is in charge of the lexers for syntax highlighting. Apparently, the designer of that lexer didn't decide to differentiate between property names and values, though it seems like a good idea. To make a suggestion for that improvement in the lexer, you'd have to go see if the most recent Scintilla JSON Lexer has already incorporated that change, and if not, put in a request with the Scintilla project. If the change is already there, or if Scintilla releases a new version with that fix for you, you would then have to ask Notepad++ developer to upgrade Scintilla to include that fix. (And the last time NPP upgraded it's Scintilla was from 3.34 to 3.56 -- about 4 years ago -- compared to the most-recent Scintilla 4.1.3)
Workaround #1: change the Style Configurator > JSON > Operator color to have something that stands out between the property and value -- maybe with a bright yellow background or something -- to make it easier for your eye to find the :
separators, at least...
Workaround #2: In the Community Forums, Claudia Frank had done some work on a PythonScript-based lexer which would allow user defined languages with regular expressions, rather than the simplistic UDL 2.1. My collection of links to her effort is at https://notepad-plus-plus.org/community/topic/16164/bug-javascript-multiline-character-not-understood-by-notepad/11. With some effort, you might be able to define the regex necessary to parse JSON in a way you like.
update: You might be able to get a UDL (User Defined Language) to do what you want. I came up with a quick one that will get the highlighting differences you described. As a nasty side effect, it breaks folding (so cannot collapse { ... }
pairs. (I tried setting the UDL folding options, but nested folds weren't working right, at least on my first attempt)
Language > Define Your Language...: Create New = JsonPropertyValues.- Operators & Delimiters
Operators 1 =, : " ' { }
, STYLER = set whatever colors you want for the punctuation
Delimiter 1 style = OPEN::
, Close =((EOL))
, STYLER = set the color you want the VALUE side to be; setNesting:
to allowOperators 1
Delimiter 2 style = OPEN:"
, Close ="
, STYLER = set the color for left-side (property) when in double-quotes, no nesting needed
Delimiter 3 style = OPEN:'
, Close ='
, STYLER = set the color for left-side (property) when in single-quotes, no nesting needed
You might want to set Nesting:
to include Numbers
on all of those STYLER entries above. And then go to the Comment & Number tab and define the STYLER to set the coloring for numbers as well.
You could set the Ext box to json
, if you want it to apply to all .JSON
files, or you could just manually apply Language > JsonPropertyValues to any JSON that you want to parse in this manner.
Anyway, this is a reasonable starting point, based on what you described; feel free to customize it or expand it beyond the features included.
add a comment |
The Scintilla component used by Notepad++ is in charge of the lexers for syntax highlighting. Apparently, the designer of that lexer didn't decide to differentiate between property names and values, though it seems like a good idea. To make a suggestion for that improvement in the lexer, you'd have to go see if the most recent Scintilla JSON Lexer has already incorporated that change, and if not, put in a request with the Scintilla project. If the change is already there, or if Scintilla releases a new version with that fix for you, you would then have to ask Notepad++ developer to upgrade Scintilla to include that fix. (And the last time NPP upgraded it's Scintilla was from 3.34 to 3.56 -- about 4 years ago -- compared to the most-recent Scintilla 4.1.3)
Workaround #1: change the Style Configurator > JSON > Operator color to have something that stands out between the property and value -- maybe with a bright yellow background or something -- to make it easier for your eye to find the :
separators, at least...
Workaround #2: In the Community Forums, Claudia Frank had done some work on a PythonScript-based lexer which would allow user defined languages with regular expressions, rather than the simplistic UDL 2.1. My collection of links to her effort is at https://notepad-plus-plus.org/community/topic/16164/bug-javascript-multiline-character-not-understood-by-notepad/11. With some effort, you might be able to define the regex necessary to parse JSON in a way you like.
update: You might be able to get a UDL (User Defined Language) to do what you want. I came up with a quick one that will get the highlighting differences you described. As a nasty side effect, it breaks folding (so cannot collapse { ... }
pairs. (I tried setting the UDL folding options, but nested folds weren't working right, at least on my first attempt)
Language > Define Your Language...: Create New = JsonPropertyValues.- Operators & Delimiters
Operators 1 =, : " ' { }
, STYLER = set whatever colors you want for the punctuation
Delimiter 1 style = OPEN::
, Close =((EOL))
, STYLER = set the color you want the VALUE side to be; setNesting:
to allowOperators 1
Delimiter 2 style = OPEN:"
, Close ="
, STYLER = set the color for left-side (property) when in double-quotes, no nesting needed
Delimiter 3 style = OPEN:'
, Close ='
, STYLER = set the color for left-side (property) when in single-quotes, no nesting needed
You might want to set Nesting:
to include Numbers
on all of those STYLER entries above. And then go to the Comment & Number tab and define the STYLER to set the coloring for numbers as well.
You could set the Ext box to json
, if you want it to apply to all .JSON
files, or you could just manually apply Language > JsonPropertyValues to any JSON that you want to parse in this manner.
Anyway, this is a reasonable starting point, based on what you described; feel free to customize it or expand it beyond the features included.
The Scintilla component used by Notepad++ is in charge of the lexers for syntax highlighting. Apparently, the designer of that lexer didn't decide to differentiate between property names and values, though it seems like a good idea. To make a suggestion for that improvement in the lexer, you'd have to go see if the most recent Scintilla JSON Lexer has already incorporated that change, and if not, put in a request with the Scintilla project. If the change is already there, or if Scintilla releases a new version with that fix for you, you would then have to ask Notepad++ developer to upgrade Scintilla to include that fix. (And the last time NPP upgraded it's Scintilla was from 3.34 to 3.56 -- about 4 years ago -- compared to the most-recent Scintilla 4.1.3)
Workaround #1: change the Style Configurator > JSON > Operator color to have something that stands out between the property and value -- maybe with a bright yellow background or something -- to make it easier for your eye to find the :
separators, at least...
Workaround #2: In the Community Forums, Claudia Frank had done some work on a PythonScript-based lexer which would allow user defined languages with regular expressions, rather than the simplistic UDL 2.1. My collection of links to her effort is at https://notepad-plus-plus.org/community/topic/16164/bug-javascript-multiline-character-not-understood-by-notepad/11. With some effort, you might be able to define the regex necessary to parse JSON in a way you like.
update: You might be able to get a UDL (User Defined Language) to do what you want. I came up with a quick one that will get the highlighting differences you described. As a nasty side effect, it breaks folding (so cannot collapse { ... }
pairs. (I tried setting the UDL folding options, but nested folds weren't working right, at least on my first attempt)
Language > Define Your Language...: Create New = JsonPropertyValues.- Operators & Delimiters
Operators 1 =, : " ' { }
, STYLER = set whatever colors you want for the punctuation
Delimiter 1 style = OPEN::
, Close =((EOL))
, STYLER = set the color you want the VALUE side to be; setNesting:
to allowOperators 1
Delimiter 2 style = OPEN:"
, Close ="
, STYLER = set the color for left-side (property) when in double-quotes, no nesting needed
Delimiter 3 style = OPEN:'
, Close ='
, STYLER = set the color for left-side (property) when in single-quotes, no nesting needed
You might want to set Nesting:
to include Numbers
on all of those STYLER entries above. And then go to the Comment & Number tab and define the STYLER to set the coloring for numbers as well.
You could set the Ext box to json
, if you want it to apply to all .JSON
files, or you could just manually apply Language > JsonPropertyValues to any JSON that you want to parse in this manner.
Anyway, this is a reasonable starting point, based on what you described; feel free to customize it or expand it beyond the features included.
edited 2 days ago
answered Jan 29 at 18:39
PeterCJPeterCJ
320310
320310
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1394957%2fdifferent-colorisation-for-json-properties-and-values%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
An issue I don't have with Xml as the text pop out of the Tag.
– Drag and Drop
Jan 16 at 14:11
Click
Language
->J
->JSON
. It should auto apply the styles to your document– Burgi
Jan 16 at 17:06
@Burgi, Well as I'm talking about the Style configurator, I thought it was obvious that the style was already selected. But it's my bad the last line can be read as "Is there a language that will provide colorisation for Json?." And the answer will be Json. Let me edit some picture to show you what i mean by more color and colorfull
– Drag and Drop
Jan 17 at 10:00
When I ask for other language it's because there were a time where colorisation from not related language gave better result on some block code. Lambda C# and Java come in mind. But that was in 2008.
– Drag and Drop
Jan 17 at 10:12
May I ask why the down vote? I know N++ is not Vim or an EDI. But simple parsing and highlight is not high evolution. Is the question not legitimate ("You don't have to do that. Copy past in your other editor that does proper higlight")? To basic - no research(Use the standard higtlight)?
– Drag and Drop
Jan 28 at 10:55