Yhyjyk

Can withdrawing asylum be illegal?

Can I visit the Trinity College (Cambridge) library and see some of their rare books

Did the new image of black hole confirm the general theory of relativity?

Can the Right Ascension and Argument of Perigee of a spacecraft's orbit keep varying by themselves with time?

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

Match Roman Numerals

Identify 80s or 90s comics with ripped creatures (not dwarves)

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

number sequence puzzle deep six

What's the point in a preamp?

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

Does Parliament hold absolute power in the UK?

Working through the single responsibility principle (SRP) in Python when calls are expensive

Word for: a synonym with a positive connotation?

Why doesn't shell automatically fix "useless use of cat"?

How to read αἱμύλιος or when to aspirate

What is the padding with red substance inside of steak packaging?

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

Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?

Could an empire control the whole planet with today's comunication methods?

What does Linus Torvalds mean when he says that Git "never ever" tracks a file?

Is there a way to generate uniformly distributed points on a sphere from a fixed amount of random real numbers per point?

different output for groups and groups USERNAME after adding a username to a group

Solving overdetermined system by QR decomposition

Fixing different display colors within string

2

$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 2 hours ago

Carl Woll

73.6k398192

asked 2 hours ago

Kevin AusmanKevin Ausman

25417

$endgroup$

add a comment | 

2

$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 2 hours ago

Carl Woll

73.6k398192

asked 2 hours ago

Kevin AusmanKevin Ausman

25417

$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 2 hours ago

Carl Woll

73.6k398192

asked 2 hours ago

Kevin AusmanKevin Ausman

25417

$endgroup$

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

share|improve this question

edited 2 hours ago

Carl Woll

73.6k398192

asked 2 hours ago

Kevin AusmanKevin Ausman

25417

share|improve this question

edited 2 hours ago

Carl Woll

73.6k398192

asked 2 hours ago

Kevin AusmanKevin Ausman

25417

edited 2 hours ago

Carl Woll

73.6k398192

edited 2 hours ago

Carl Woll

73.6k398192

asked 2 hours ago

Kevin AusmanKevin Ausman

25417

asked 2 hours ago

Kevin AusmanKevin Ausman

25417

1 Answer
1

active

oldest

votes

4

$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 2 hours ago

Carl WollCarl Woll

73.6k398192

$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
  2 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  1 hour ago
  

  
  
  
  

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

4

$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 2 hours ago

Carl WollCarl Woll

73.6k398192

$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
  2 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  1 hour ago
  

  
  
  
  

add a comment | 

4

$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 2 hours ago

Carl WollCarl Woll

73.6k398192

$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
  2 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  $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
  1 hour ago
  

  
  
  
  

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 2 hours ago

Carl WollCarl Woll

73.6k398192

$endgroup$

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

share|improve this answer

answered 2 hours ago

Carl WollCarl Woll

73.6k398192

answered 2 hours ago

Carl WollCarl Woll

73.6k398192

answered 2 hours ago

Carl WollCarl Woll

73.6k398192