Regarding how to write general math expressions on the site, my answer here covers that well I think. Specifically for tables, you can use LaTeX's \array command. The tabular command, which only works in text mode, is not available here, so if you want to include text in your table, you will have to do some tinkering. Here is an example table: $$\begin{...


Testing alternate way of implementing spoiler $$ \require{action} \require{enclose} \toggle{ x\cdot 0 = 0\quad\enclose{roundedbox}{\text{ Click this for derivation }} }{ \begin{array}{rll} x\cdot 0 &= \mathtip{x\cdot 0 + 0}{0 \text{ is additive identity}} \\ &= \mathtip{x\cdot 0 + (x\cdot 0 + -(x\cdot 0))}{ -(x\cdot 0) \text{ is additive inverse ...


There are three approaches for line breaks. As pointed out in the comments, Approaches 2 and 3 produce the same HTML output when rendered on the page. Approach 1: Press "Enter" twice Output: Hi Bye Code: Hi Bye Approach 2: Two spaces at end of line Output: Hi Bye Code: Hi Bye There are two spaces after "Hi." That is, the text looks like: Hi&...


You can begin every line with >! and end it with two spaces.  


A problem is that it is not a semantically correct use. At the moment the formatting used by SE on this site for block-quotes is such that optically its usage for emphasis makes sense. Yet, this could change at any point in time. Moreover, already now I feel it is not really the case on the mobile site. In addition, imagine some machine reads the site to ...


Simple solution: don't abuse MathJax to colour your text.


The commands \lbrack and \rbrack are macros that produce [ and ] respectively, and MathJax has no problem when you use them instead of the symbols - see the comment below, which was produced by For any $a,b\in \lbrack 0,x)$: $a\vee b$ exists. Namely, $a\vee b=\max\{a,b\}$. You might be asking about when directed sets are [complete](http://en.wikipedia.org/...


Use mathjax for mathematics, not for text formatting. The mathjax italics happen because mathjax thinks "abcde" is just a string of variables.


Use Markdown's inline link syntax, an example of which is shown when you click the "help" link under "Add Comment". [link text](http://link-uri.com) This works in answers as well.


Thinking about it, I also realize that we could $\Large\text{use LaTeX}$ in ways that are $\Huge\text{still of questionable merit}$, but which fit inline. Note that we can't ${\fontsize{3cm}{1em}\selectfont use an arbitrary fontsize}$. But then again, some might ask $\Tiny\text{why we would do this at all.}$


For F.Zer \begin{align} f(x:xs) &= \sum_{i:\ 0 \leq i < \#(x:xs)} (x:xs).i * (i + 1)\\ &=\sum_{i:\ i =0} (x:xs).i * (i + 1)+\sum_{i:\ 1\le i<\#xs+1}(x:xs).i * (i + 1)\\ &=x + \sum_{i:\ 1 \leq i \le \#xs} xs.(i-1) * (i + 1)\\ &=x + \sum_{j:\ 0 \leq j < \#xs} xs.j * (j + 2)\quad\quad(\text{Here }j=i-1\text{ and }i\text{ is replaced ...


I don't there's been any recent change; this is how things have always worked. To get a single line break, put two spaces at the end of the line - for example, **Theorem** adsfdf *proof*: asdfdsaf produces Theorem adsfdf proof: asdfdsaf


Line breaks and many other stuff are not supported in comments. The basic design rationale is (as described by SE) that comments should be short and sweet: if you need to start a new paragraph, either you are really writing an answer (and so should be posting as such) or you are being too verbose in the comments.


You can quote by simply using quotation marks. You can write a link in a post or comment like [this](url here), for example google link.


When I look at the specific comment you linked to, I think that the only problems is that you did not include http:// at the beginning of the link. You wrote this: [ArtOfProblemSolving forum](www.artofproblemsolving.com/Forum/viewtopic.php?p=3542095&sid=61650444d5d??5e56fb5c71a50982e4912#p3542095) which does not work: ArtOfProblemSolving forum. If you ...


I've gone an updated the CSS for spoilers - there was something overriding the spoiler CSS in this instance. With you in the next build (rev. 2017.3.14.*)


The former is a block quote the later is a spoiler. There is also preformatted text, which might qualify. It looks like this. This is preformatted text. It is especially useful for code. You can get it by indenting the text with four spaces. A feature or issue with this is that it will not break you lines, but instead will add a slider. Like this. This ...


The best thing I can think of     is to end the preceding line with two whitespaces        (which creates a single line break)           and copy-paste several &nbsp; at the beginning of next line. (Turns out this is same method as in the link Martin posted.)


I suppose if you really wanted to Then you could vary it up by abusing headers But this hurts my sensibilities


It seems to be that if you do >! at the beginning of a line, you get that. You could have found that out by clicking edit post and looking at the source. for example.


This answer to a similar question (as linked to in the comments by Martin Sleziak) suggests the hack of $$\tag*{$\blacksquare$}$$, which looks like the following: ...and the proof is complete. $\tag*{$\blacksquare$}$ Frustratingly, it takes a new line. But I do not think this is an issue, as issues go!


Line-breaks and paragraphs in comments are not supported. The shift-enter is intended only to affect the situation while you edit. It is possible to work around this restriction via using MathJax. But doinng so is discouraged. If you need some visual separation, use some symbols for example // like this: This is one important remark I want to make and ...


The handling of MathJax in Markdown is rather awkward, since TeX and Markdown have different interpretations for things like underscores. You need to keep Mardown from processing those character inside of mathematics, and the way it works on StackExchange is that the mathematics is removed before Markdown runs, and then reinserted after the Markdown ...

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