You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I am annotating something, I often come into the following situation:
I have an annotation I want to make but I realize that the two choices are morally the same symbol, and (in this case) 0 should import 1. In this case, I would like to type 01# to be placed in an editor of my choice (probably via the $EDITIOR environment variable) with both of the files loaded so that I can remedy the situation before I go on annotating. In this case I would import the mv module from smglom/mv in mathtalk.en.tex and remove the \symdecl*{iff} there. This is short and painless and gets rid of an otherwise annoying quality issue then and there.
Of course in the example above, there might also be three or more files involved (or choice numbers larger than digits), so we need to generalize the interaction slightly.
This could build on #27, so that should be done first.
The text was updated successfully, but these errors were encountered:
When I am annotating something, I often come into the following situation:
I have an annotation I want to make but I realize that the two choices are morally the same symbol, and (in this case)
0
should import1
. In this case, I would like to type01#
to be placed in an editor of my choice (probably via the$EDITIOR
environment variable) with both of the files loaded so that I can remedy the situation before I go on annotating. In this case I would import themv
module fromsmglom/mv
inmathtalk.en.tex
and remove the\symdecl*{iff}
there. This is short and painless and gets rid of an otherwise annoying quality issue then and there.Of course in the example above, there might also be three or more files involved (or choice numbers larger than digits), so we need to generalize the interaction slightly.
This could build on #27, so that should be done first.
The text was updated successfully, but these errors were encountered: