8

Another workaround is to encode the "$" as "%24" in the URL: [`MachineEpsilon`](http://reference.wolfram.com/language/ref/%24MachineEpsilon.html), $\epsilon$ is $2^{-52}$.


6

This seems to be a work-around. [image follows] [end image]


4

For one we have this old question of mine which seemed fixed. Then, we have an issue with dollar signs in code blocks that can sometimes to solved by additionally indenting the block. Other than that, I have issues when my code-blocks contain dollar signs (this is only a sample code..): This is annoying too since I finally moved to use dollar-variables like ...


4

A distinctive color scheme is definitely necessary (especially with the recent tendency towards low-contrast...). At least on the main site the approach of putting code output inside quotes is more distinctive than here on meta: Here's a quote containing some code Can anyone actually see that change in gray level??


2

Update m_golberg points out that there's another way to get in a <br/>, namely by using two spaces before the newline, i.e. \n. So we can use this: - `DumpSave` is not portable enough - `Save` saves `$Context` and `$ContextPath` (everything what is not protected) together with all definitions so loading it will affect environment. I can load it ...


1

This is my attempt to look further into the point made by blockwave. Let's look at how the following raw text will be formatted. Text The quick red fox jumped over the lazy dog. The quick red fox jumped over the lazy dog. The quick red fox jumped over the lazy dog. >The quick red fox jumped over the lazy dog. The quick red fox jumped over the lazy dog. ...


Only top voted, non community-wiki answers of a minimum length are eligible