6,680 reputation
1640
bio website
location Cambridge, United Kingdom
age
visits member for 3 years, 8 months
seen 1 hour ago

Researcher in quantum information --- involving algebras over finite dimensional Hilbert spaces, graphs and combinatorics, and vector spaces over ℤ/pℤ.

I habitually edit and re-edit anything I write, as long as I have the time, interest, and ability. I should probably apologize for this tendency, but you will probably have to be satisfied with being warned about it instead.


May
28
revised Short names for macros
fixed url
May
28
comment Short names for macros
@Jukka: I have expanded my answer to incorporate using # as a character for macros in mathmode and displayed equations. (Barring any technical problems with my answer, I expect this will be my final revision.)
May
28
revised Short names for macros
simplified a phrase slightly
May
28
comment Short names for macros
Is there really such a thing as an exhaustive list of tricks? And if you think there is, do you intend to award the bounty to the one who accumulates them all into a single monolithic answer? I think it's better to have a collection of answers who each take some approach, and refine that one approach as much as possible.
May
28
comment Short names for macros
@Bruno: I know that its feasible, but given that the original point is to deal with very short macros, I don't feel the need to go the next step towards creating an entirely separate namespace for arbitrary macro names. I'm content with solving the problem of creating an alternative means of defining one-character macro names. If Jukka feels that it's that important to have another means of defining multi-character macros, I'm content to allow someone else to go for the bounty.
May
28
accepted Side-by-side source and output when documenting a style file
May
28
comment Short names for macros
@David: I attest that it really does help. I routinely use \C as shorthand for \mathbb C, and \x for \times. This is as close as one can get with a standard keyboard to having the same orthography as I type that I would have on a chalkboard. I then spend more time concentrating on what it is I want to write if the objects I refer to over, and over, and over again have names which are as simple as possible. If your mental name for "the complex numbers" is the glyph ℂ, why give it a more complex name? So long as the name visually represents how it is typeset, this is not unreasonable.
May
28
comment Short names for macros
@Jukka: I have now modified the code to consume trailing whitespace, in the case (zero-parameter macros) in which they originally failed to do so. Thanks for pointing that out; consistency of behaviour really is desirable here I think.
May
28
revised Short names for macros
improved the code, and elaborated on the differences between the macros defined here and normal control sequences
May
28
comment Short names for macros
@Jukka: you make good points with respect to the difference between this way of forming macros. I will emphasize these differences.
May
28
awarded  Nice Answer
May
28
comment Side-by-side source and output when documenting a style file
@Martin: I'm just going to take that to mean that the only problems I am likely to have, is that docstrip will stymie any attempts to have comments in the content of a LTXexample environment. I was concerned that you were hinting at additional problems.
May
28
comment Side-by-side source and output when documenting a style file
@Martin: I'm familiar with the stripping of % out of the documentation, which is of course the context in which I'll be using showexpl; for the time being I may be able to deal with example code that contains no comments. However, now I'm more concerned about your remarks about showexpl taking the comments of the documentation lines verbatim: wouldn't the functionality of showexpl only be engaged when all of the % characters have been stripped anyhow?
May
28
comment Side-by-side source and output when documenting a style file
@Martin: the problems with showexpl... I assume the problem is only with comments in the sample code being displayed itself, am I right?
May
28
revised Side-by-side source and output when documenting a style file
fixed URL to the sverb package documentation
May
28
suggested suggested edit on Side-by-side source and output when documenting a style file
May
28
comment Side-by-side source and output when documenting a style file
@xport: that's a question about just showing the source-code. Mine is somewhat more precise in that it requires side-by-side displaying of LaTeX code, and Seamus' answer happens to suggest the same tool as the answer you've linked to.
May
28
revised Side-by-side source and output when documenting a style file
corrected typo
May
28
asked Side-by-side source and output when documenting a style file
May
27
awarded  Cleanup