Fixing different display colors within string Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Sequential subscripts etc. in a unified notationHow to overload System`StringJoin to automatically use ToString on arguments?Counting the number of instances of one sub-string within a given string within a lower- and upper-bound gap of a second sub-stringDisplay problem multiplying matrixEvaluate within HoldStringSplit acting weird on a String in StandardForm3D image display with different viewpointsApplying different values to string rowFormatting Display PrecisionInconsistent behaviour using string with superscript as labelPreventing single letter italics within a string
Is a ledger board required if the side of my house is wood?
How to tell that you are a giant?
Generate an RGB colour grid
If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?
Drawing without replacement: why is the order of draw irrelevant?
Chinese Seal on silk painting - what does it mean?
Why wasn't DOSKEY integrated with COMMAND.COM?
An adverb for when you're not exaggerating
Can anything be seen from the center of the Boötes void? How dark would it be?
Significance of Cersei's obsession with elephants?
Why does it sometimes sound good to play a grace note as a lead in to a note in a melody?
Denied boarding although I have proper visa and documentation. To whom should I make a complaint?
Take 2! Is this homebrew Lady of Pain warlock patron balanced?
Crossing US/Canada Border for less than 24 hours
Why weren't discrete x86 CPUs ever used in game hardware?
Amount of permutations on an NxNxN Rubik's Cube
Should I use a zero-interest credit card for a large one-time purchase?
How fail-safe is nr as stop bytes?
Is it fair for a professor to grade us on the possession of past papers?
As a beginner, should I get a Squier Strat with a SSS config or a HSS?
Disembodied hand growing fangs
Can a new player join a group only when a new campaign starts?
Is there a kind of relay only consumes power when switching?
Does the Weapon Master feat grant you a fighting style?
Fixing different display colors within string
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Sequential subscripts etc. in a unified notationHow to overload System`StringJoin to automatically use ToString on arguments?Counting the number of instances of one sub-string within a given string within a lower- and upper-bound gap of a second sub-stringDisplay problem multiplying matrixEvaluate within HoldStringSplit acting weird on a String in StandardForm3D image display with different viewpointsApplying different values to string rowFormatting Display PrecisionInconsistent behaviour using string with superscript as labelPreventing single letter italics within a string
$begingroup$
My question below is my attempt to reduce a problem I am having to the simplest possible version that will show the error I am trying to fix. I recognize that the coding looks tortured, and I will provide at the end an explanation for why I am doing it this way, but hopefully we can just focus on the particular behavior in my abstracted example.
(copyable version below)
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False
]
Why is the "O (g)" black and the rest of the string grey? And how do I change it so that it all displays as black?
Background: This is a follow-up to this thread. I am using the strings as a way to define palette-selectable labels that preserve non-Mathematica-standard notation that I can then use with the Notation package to associate this alternate notation (both input and output) with more standard symbols that can be used internally. I need the label to be in a string so that the notational form is maintained without parsing once it is interpreted by a ParsedBoxWrapper@TemplateBox, and I use a custom style to suppress the display of those quotation marks.
Edit: I originally had this including """<>string<>""", but have since discovered that the extra quotes aren't necessary to make the problem happen.
string-manipulation display
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
$endgroup$
add a comment |
$begingroup$
My question below is my attempt to reduce a problem I am having to the simplest possible version that will show the error I am trying to fix. I recognize that the coding looks tortured, and I will provide at the end an explanation for why I am doing it this way, but hopefully we can just focus on the particular behavior in my abstracted example.
(copyable version below)
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False
]
Why is the "O (g)" black and the rest of the string grey? And how do I change it so that it all displays as black?
Background: This is a follow-up to this thread. I am using the strings as a way to define palette-selectable labels that preserve non-Mathematica-standard notation that I can then use with the Notation package to associate this alternate notation (both input and output) with more standard symbols that can be used internally. I need the label to be in a string so that the notational form is maintained without parsing once it is interpreted by a ParsedBoxWrapper@TemplateBox, and I use a custom style to suppress the display of those quotation marks.
Edit: I originally had this including """<>string<>""", but have since discovered that the extra quotes aren't necessary to make the problem happen.
string-manipulation display
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
$endgroup$
add a comment |
$begingroup$
My question below is my attempt to reduce a problem I am having to the simplest possible version that will show the error I am trying to fix. I recognize that the coding looks tortured, and I will provide at the end an explanation for why I am doing it this way, but hopefully we can just focus on the particular behavior in my abstracted example.
(copyable version below)
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False
]
Why is the "O (g)" black and the rest of the string grey? And how do I change it so that it all displays as black?
Background: This is a follow-up to this thread. I am using the strings as a way to define palette-selectable labels that preserve non-Mathematica-standard notation that I can then use with the Notation package to associate this alternate notation (both input and output) with more standard symbols that can be used internally. I need the label to be in a string so that the notational form is maintained without parsing once it is interpreted by a ParsedBoxWrapper@TemplateBox, and I use a custom style to suppress the display of those quotation marks.
Edit: I originally had this including """<>string<>""", but have since discovered that the extra quotes aren't necessary to make the problem happen.
string-manipulation display
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
$endgroup$
My question below is my attempt to reduce a problem I am having to the simplest possible version that will show the error I am trying to fix. I recognize that the coding looks tortured, and I will provide at the end an explanation for why I am doing it this way, but hopefully we can just focus on the particular behavior in my abstracted example.
(copyable version below)
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False
]
Why is the "O (g)" black and the rest of the string grey? And how do I change it so that it all displays as black?
Background: This is a follow-up to this thread. I am using the strings as a way to define palette-selectable labels that preserve non-Mathematica-standard notation that I can then use with the Notation package to associate this alternate notation (both input and output) with more standard symbols that can be used internally. I need the label to be in a string so that the notational form is maintained without parsing once it is interpreted by a ParsedBoxWrapper@TemplateBox, and I use a custom style to suppress the display of those quotation marks.
Edit: I originally had this including """<>string<>""", but have since discovered that the extra quotes aren't necessary to make the problem happen.
string-manipulation display
string-manipulation display
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
edited Apr 12 at 19:26
Carl Woll
74.6k3100194
74.6k3100194
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
asked Apr 12 at 18:58
Kevin AusmanKevin Ausman
35417
35417
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
$begingroup$
Short answer: You need to turn off auto styles:
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False,
ShowAutoStyles->False
]
The issue is that your string, inside of an "Input" cell is not interpreted as a string, it is interpreted as an expression, and so the default syntax coloring happens.
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
$endgroup$
$begingroup$
Magnificent! Thank you! It seems that this fix does not correct a related problem that I assumed would be automatically fixed when the coloration-problem was corrected. I will update my question with an example of that issue.
$endgroup$
– Kevin Ausman
Apr 12 at 19:44
$begingroup$
Actually, I will add my new question as a separate question rather than editing this one, since it looks like it is unrelated. Thank you.
$endgroup$
– Kevin Ausman
Apr 12 at 19:51
$begingroup$
I guess the bigger question might be whether or not there is a way to force a string in an input cell to be interpreted as a string rather than interpreted as an expression, because that might separately solve both this question and the other one that I recently added.
$endgroup$
– Kevin Ausman
Apr 12 at 20:01
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "387"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fmathematica.stackexchange.com%2fquestions%2f195087%2ffixing-different-display-colors-within-string%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
$begingroup$
Short answer: You need to turn off auto styles:
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False,
ShowAutoStyles->False
]
The issue is that your string, inside of an "Input" cell is not interpreted as a string, it is interpreted as an expression, and so the default syntax coloring happens.
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
$endgroup$
$begingroup$
Magnificent! Thank you! It seems that this fix does not correct a related problem that I assumed would be automatically fixed when the coloration-problem was corrected. I will update my question with an example of that issue.
$endgroup$
– Kevin Ausman
Apr 12 at 19:44
$begingroup$
Actually, I will add my new question as a separate question rather than editing this one, since it looks like it is unrelated. Thank you.
$endgroup$
– Kevin Ausman
Apr 12 at 19:51
$begingroup$
I guess the bigger question might be whether or not there is a way to force a string in an input cell to be interpreted as a string rather than interpreted as an expression, because that might separately solve both this question and the other one that I recently added.
$endgroup$
– Kevin Ausman
Apr 12 at 20:01
add a comment |
$begingroup$
Short answer: You need to turn off auto styles:
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False,
ShowAutoStyles->False
]
The issue is that your string, inside of an "Input" cell is not interpreted as a string, it is interpreted as an expression, and so the default syntax coloring happens.
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
$endgroup$
$begingroup$
Magnificent! Thank you! It seems that this fix does not correct a related problem that I assumed would be automatically fixed when the coloration-problem was corrected. I will update my question with an example of that issue.
$endgroup$
– Kevin Ausman
Apr 12 at 19:44
$begingroup$
Actually, I will add my new question as a separate question rather than editing this one, since it looks like it is unrelated. Thank you.
$endgroup$
– Kevin Ausman
Apr 12 at 19:51
$begingroup$
I guess the bigger question might be whether or not there is a way to force a string in an input cell to be interpreted as a string rather than interpreted as an expression, because that might separately solve both this question and the other one that I recently added.
$endgroup$
– Kevin Ausman
Apr 12 at 20:01
add a comment |
$begingroup$
Short answer: You need to turn off auto styles:
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False,
ShowAutoStyles->False
]
The issue is that your string, inside of an "Input" cell is not interpreted as a string, it is interpreted as an expression, and so the default syntax coloring happens.
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
$endgroup$
Short answer: You need to turn off auto styles:
CellPrint @ ExpressionCell[
"!(*SubscriptBox[(H), (2)])O (H)",
"Input",
ShowStringCharacters->False,
ShowAutoStyles->False
]
The issue is that your string, inside of an "Input" cell is not interpreted as a string, it is interpreted as an expression, and so the default syntax coloring happens.
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
answered Apr 12 at 19:24
Carl WollCarl Woll
74.6k3100194
74.6k3100194
$begingroup$
Magnificent! Thank you! It seems that this fix does not correct a related problem that I assumed would be automatically fixed when the coloration-problem was corrected. I will update my question with an example of that issue.
$endgroup$
– Kevin Ausman
Apr 12 at 19:44
$begingroup$
Actually, I will add my new question as a separate question rather than editing this one, since it looks like it is unrelated. Thank you.
$endgroup$
– Kevin Ausman
Apr 12 at 19:51
$begingroup$
I guess the bigger question might be whether or not there is a way to force a string in an input cell to be interpreted as a string rather than interpreted as an expression, because that might separately solve both this question and the other one that I recently added.
$endgroup$
– Kevin Ausman
Apr 12 at 20:01
add a comment |
$begingroup$
Magnificent! Thank you! It seems that this fix does not correct a related problem that I assumed would be automatically fixed when the coloration-problem was corrected. I will update my question with an example of that issue.
$endgroup$
– Kevin Ausman
Apr 12 at 19:44
$begingroup$
Actually, I will add my new question as a separate question rather than editing this one, since it looks like it is unrelated. Thank you.
$endgroup$
– Kevin Ausman
Apr 12 at 19:51
$begingroup$
I guess the bigger question might be whether or not there is a way to force a string in an input cell to be interpreted as a string rather than interpreted as an expression, because that might separately solve both this question and the other one that I recently added.
$endgroup$
– Kevin Ausman
Apr 12 at 20:01
$begingroup$
Magnificent! Thank you! It seems that this fix does not correct a related problem that I assumed would be automatically fixed when the coloration-problem was corrected. I will update my question with an example of that issue.
$endgroup$
– Kevin Ausman
Apr 12 at 19:44
$begingroup$
Magnificent! Thank you! It seems that this fix does not correct a related problem that I assumed would be automatically fixed when the coloration-problem was corrected. I will update my question with an example of that issue.
$endgroup$
– Kevin Ausman
Apr 12 at 19:44
$begingroup$
Actually, I will add my new question as a separate question rather than editing this one, since it looks like it is unrelated. Thank you.
$endgroup$
– Kevin Ausman
Apr 12 at 19:51
$begingroup$
Actually, I will add my new question as a separate question rather than editing this one, since it looks like it is unrelated. Thank you.
$endgroup$
– Kevin Ausman
Apr 12 at 19:51
$begingroup$
I guess the bigger question might be whether or not there is a way to force a string in an input cell to be interpreted as a string rather than interpreted as an expression, because that might separately solve both this question and the other one that I recently added.
$endgroup$
– Kevin Ausman
Apr 12 at 20:01
$begingroup$
I guess the bigger question might be whether or not there is a way to force a string in an input cell to be interpreted as a string rather than interpreted as an expression, because that might separately solve both this question and the other one that I recently added.
$endgroup$
– Kevin Ausman
Apr 12 at 20:01
add a comment |
Thanks for contributing an answer to Mathematica Stack Exchange!
- 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.
Use MathJax to format equations. MathJax reference.
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%2fmathematica.stackexchange.com%2fquestions%2f195087%2ffixing-different-display-colors-within-string%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
