% usual scoping rules. Both of these commands have corresponding
% environments with the same names (without the leading `|\|', obviously).
%
% usual scoping rules. Both of these commands have corresponding
% environments with the same names (without the leading `|\|', obviously).
%
%
% As an example, the following command makes @.{"@/"<text>"/"} write its
% argument \<text> in italics:
%
% As an example, the following command makes @.{"@/"<text>"/"} write its
% argument \<text> in italics:
% use fragile commands in their definitions. Unless you start doing very
% strange things, @-commands never need |\protect|ing.
%
% use fragile commands in their definitions. Unless you start doing very
% strange things, @-commands never need |\protect|ing.
%
%
% A small number of hopefully useful commands are provided by default.
% These are described in the table below:
%
% A small number of hopefully useful commands are provided by default.
% These are described in the table below:
%
% We want all @-commands to be robust. We could leave them all being
% fragile, although making robust @-commands would then be almost impossible.
%
% We want all @-commands to be robust. We could leave them all being
% fragile, although making robust @-commands would then be almost impossible.
-% Since we gobbled the |\fi| from the above, we must put that back. We then
-% need to do things which are more complicated. If |\protect| is behaving
+% Since we gobbled the |\fi| from the above, we must put that back. We then
+% need to do things which are more complicated. If |\protect| is behaving
% like |\string|, then we do one sort of protection. Otherwise, we assume
% that |\protect| is being like |\noexpand|.
%
% like |\string|, then we do one sort of protection. Otherwise, we assume
% that |\protect| is being like |\noexpand|.
%