Ttyjfyk

How many people can fit inside Mordenkainen's Magnificent Mansion?

How to split my screen on my Macbook Air?

Can smartphones with the same camera sensor have different image quality?

Does Parliament need to approve the new Brexit delay to 31 October 2019?

Did God make two great lights or did He make the great light two?

Do warforged have souls?

Can the prologue be the backstory of your main character?

Windows 10: How to Lock (not sleep) laptop on lid close?

Match Roman Numerals

Mortgage adviser recommends a longer term than necessary combined with overpayments

Sort a list of pairs representing an acyclic, partial automorphism

What's the point in a preamp?

How did passengers keep warm on sail ships?

ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?

What do you call a plan that's an alternative plan in case your initial plan fails?

How to delete random line from file using Unix command?

Why can't wing-mounted spoilers be used to steepen approaches?

Why does this iterative way of solving of equation work?

Is there a writing software that you can sort scenes like slides in PowerPoint?

how can a perfect fourth interval be considered either consonant or dissonant?

How to test the equality of two Pearson correlation coefficients computed from the same sample?

What aspect of planet Earth must be changed to prevent the industrial revolution?

Semisimplicity of the category of coherent sheaves?

How long does the line of fire that you can create as an action using the Investiture of Flame spell last?

Fixing different display colors within string

3

$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

share|improve this question

edited yesterday

Carl Woll

73.9k398192

asked yesterday

Kevin AusmanKevin Ausman

26917

$endgroup$

add a comment | 

3

$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

share|improve this question

edited yesterday

Carl Woll

73.9k398192

asked yesterday

Kevin AusmanKevin Ausman

26917

$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

share|improve this question

edited yesterday

Carl Woll

73.9k398192

asked yesterday

Kevin AusmanKevin Ausman

26917

$endgroup$

CellPrint @ ExpressionCell[
 "!(*SubscriptBox[(H), (2)])O (H)",
 "Input",
 ShowStringCharacters->False
]

share|improve this question

edited yesterday

Carl Woll

73.9k398192

asked yesterday

Kevin AusmanKevin Ausman

26917

share|improve this question

edited yesterday

Carl Woll

73.9k398192

asked yesterday

Kevin AusmanKevin Ausman

26917

edited yesterday

Carl Woll

73.9k398192

edited yesterday

Carl Woll

73.9k398192

asked yesterday

Kevin AusmanKevin Ausman

26917

asked yesterday

Kevin AusmanKevin Ausman

26917

1 Answer
1

active

oldest

votes

6

$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.

share|improve this answer

answered yesterday

Carl WollCarl Woll

73.9k398192

$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
  yesterday
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  yesterday
  

  
  
  
  

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
);



);

draft saved

draft discarded

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

Name

Email

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

Name

Email

Required, but never shown

6

$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.

share|improve this answer

answered yesterday

Carl WollCarl Woll

73.9k398192

$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
  yesterday
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  yesterday
  

  
  
  
  

add a comment | 

6

$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.

share|improve this answer

answered yesterday

Carl WollCarl Woll

73.9k398192

$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
  yesterday
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  yesterday
  

  
  
  
  

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.

share|improve this answer

answered yesterday

Carl WollCarl Woll

73.9k398192

$endgroup$

CellPrint @ ExpressionCell[
 "!(*SubscriptBox[(H), (2)])O (H)",
 "Input",
 ShowStringCharacters->False,
 ShowAutoStyles->False
]

share|improve this answer

answered yesterday

Carl WollCarl Woll

73.9k398192

answered yesterday

Carl WollCarl Woll

73.9k398192

answered yesterday

Carl WollCarl Woll

73.9k398192