In this comment Yuhao Huang suggests we could start having some standard macros in algebraic geometry. I have two comments:
- It makes sense to reserve some commands such as
\Spec
and \colim
- It doesn’t make sense, I think, to fix the actual macros for these commands.
I think I can convince most of you to agree with 2. For example, I like to define
\def\Spec{\mathop{\rm Spec}}
but (and I am happy to get feedback) I am sure this is completely utterly totally wrong! And let’s not even talk about
\def\SheafHom{\mathop{\mathcal{H}\!{\it om}}\nolimits}
which I am sure you like to define with an underline or a squiggly underline. It is clear that we are never ever going to agree on the “correct” macro even for something as simple as \Spec
. Right?
I think I can make some argument for 1, but I agree it isn’t so clear. Namely, wouldn’t it be nice if you could download another algebraic geometer’s latex code and run it locally on you machine with your own preamble? After all, my preamble is better than yours (as we’ve already discussed above).
Finally, many people define macros for things that take just one letter, typically with something like
\newcommand{\CC}{\mathbb{C}}
I may have done this myself in the past. But now I think just typing \mathbb{C}
is just as fast and it makes it clear what you get. The argument that it is faster to change the macro doesn’t really hold water as you can do a search and replace (or run a sed command) quite easily. Moreover, the letter C is going to occur as blackboard bold, gothic, greek, german, calligraphic, italic, roman, etc, etc so don’t try to tell me that it is better to use a short macro because who knows which of \CC, \bC, \cC, \iC
is the one you want? No, the only reason for having a macro for blackboard bold C is if you wanted to have a macro for the complex numbers. Then you would probably name it \ComplexNumbers
or something long like that so you never get confused.
I guess then the question becomes: Is \ComplexNumbers
a good choice for one of the standard command names? I’m not convinced.
Another aspect of the situation is that, if we are inclined to introduce the command \ComplexNumbers
, then also some things that never get macros should get macros. For example there should probably be a macro (untested)
\def\DerivedCategory#1{\mathop{\rm D}(#1)}
because part of the value of having macros may be that it makes it easier for our LaTeX files to be parsed by machines in the future. Madness!
I hope there is a lot here you can disagree with. My stance on most of this stuff is that it is much easier to fix this kind of thing (if it turns out we made a bad choice of coding a symbol or whatever), than it is to add new mathematics. So essentially, it doesn’t matter, but I am still interested to hear if you more or less agree with what I said above. Leave a comment!
PS: Here is a complete list of the currently defined macros in the Stacks project: \lim, \colim, \Spec, \Hom, \SheafHom, \Sch, \Mor, \Ob, \Sh
. You can find these in preamble.tex.
PPS: Of course there is the whole other issue of choice of macro names. As you can see above I have been tempted by the Capitalization Curse. Why didn’t we name the macros \lim, \colim, \spec, \hom, \sheafhom, \sch, \mor, \ob, \sh
? I guess an easy way out is to simply have both?