network profile
| bio | website | dnquark.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 4 months |
| seen | Mar 25 '12 at 21:20 | |
| stats | profile views | 13 |
{physicist, programmer, data scientist}
|
Oct 14 |
awarded | Popular Question |
|
May 15 |
awarded | Yearling |
|
Oct 6 |
awarded | Nice Question |
|
Apr 21 |
awarded | Teacher |
|
Apr 21 |
accepted | Standalone compilation of sources intended for \input{} or \include{} |
|
Apr 21 |
answered | Standalone compilation of sources intended for \input{} or \include{} |
|
Apr 15 |
asked | Standalone compilation of sources intended for \input{} or \include{} |
|
Jan 27 |
comment |
Definining commands/abbreviations that contain numbers @Hendrik: how about H2O? :) (I am not a chemist, so I actually don't care much about that one.) In truth, almost all my use cases involve subscripts and superscripts -- perhaps used as powers or to indicate matrix elements. So \newcommand parameters will work well. |
|
Jan 27 |
comment |
Definining commands/abbreviations that contain numbers Jan's answer works well for many of my use cases; it looks to me like other solutions are cumbersome or have side effects. I often use variables/identifiers with numbers when I compute things, and it is annoying that I cannot reuse these names in LaTeX -- that was my main motivation for asking the question. For the time being I think I'll stick with either not using numbers, or using command parameters as per Jan's suggestion. |
|
Jan 27 |
awarded | Scholar |
|
Jan 27 |
accepted | Definining commands/abbreviations that contain numbers |
|
Jan 26 |
awarded | Student |
|
Jan 26 |
asked | Definining commands/abbreviations that contain numbers |
|
Jan 18 |
awarded | Supporter |
