pms.cls: Do not define \e for \emph

This is only used a few times, so a shorthand is not needed.
(We really should get rid of \i and \t as well, because redefining
LaTeX internal commands sucks.)

Signed-off-by: Ulrich Müller <ulm@gentoo.org>

10 files changed, 13 insertions, 14 deletions

diff --git a/appendices.tex b/appendices.tex
index 21716d6..3d2ef52 100644
--- a/appendices.tex
+++ b/appendices.tex
@@ -52,7 +52,7 @@ DEPEND="
 
 \subsection{CVS versions}
 Portage has very crude support for CVS packages. The package \t{foo} could contain a file named
-\t{foo-cvs.1.2.3.ebuild}. This version would order \e{higher} than any non-CVS version (including
+\t{foo-cvs.1.2.3.ebuild}. This version would order \emph{higher} than any non-CVS version (including
 \t{foo-2.ebuild}). This feature has not seen real world use and breaks versioned dependencies, so
 it must not be used.
 
diff --git a/dependencies.tex b/dependencies.tex
index a641014..557ddce 100644
--- a/dependencies.tex
+++ b/dependencies.tex
@@ -377,8 +377,8 @@ Multiple requirements may be combined using commas, e.\,g.\ \t{[first,-second,th
 When multiple requirements are specified, all must match for a successful match.
 
 \featurelabel{use-dep-defaults} In a 4-style use dependency, the flag name may immediately be
-followed by a \e{default} specified by either \t{(+)} or \t{(-)}. The former indicates that, when
-applying the use dependency to a package that does not have the flag in question in
+followed by a \emph{default} specified by either \t{(+)} or \t{(-)}. The former indicates that,
+when applying the use dependency to a package that does not have the flag in question in
 \t{IUSE_REFERENCEABLE}, the package manager shall behave as if the flag were present and enabled;
 the latter, present and disabled.
 
diff --git a/ebuild-env-state.tex b/ebuild-env-state.tex
index 34c41c4..a998660 100644
--- a/ebuild-env-state.tex
+++ b/ebuild-env-state.tex
@@ -5,7 +5,7 @@ Exported and default scope variables are saved between functions. A non-local va
 function earlier in the call sequence must have its value preserved for later functions, including
 functions executed as part of a later uninstall.
 
-\note{\t{pkg_pretend} is \e{not} part of the normal call sequence, and does not take part in
+\note{\t{pkg_pretend} is \emph{not} part of the normal call sequence, and does not take part in
 environment saving.}
 
 Variables that were exported must remain exported in later functions; variables with default
diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
index 2736423..332c3d8 100644
--- a/ebuild-env-vars.tex
+++ b/ebuild-env-vars.tex
@@ -421,7 +421,7 @@ installing a package. Details are beyond the scope of this specification.
 
 \featurelabel{replace-version-vars} In EAPIs listed in table~\ref{tab:added-env-vars-table} as
 supporting it, the \t{REPLACING_VERSIONS} variable shall be defined in \t{pkg_preinst} and
-\t{pkg_postinst}.  In addition, it \e{may} be defined in \t{pkg_pretend} and \t{pkg_setup},
+\t{pkg_postinst}. In addition, it \emph{may} be defined in \t{pkg_pretend} and \t{pkg_setup},
 although ebuild authors should take care to handle binary package creation and installation
 correctly when using it in these phases.
 
diff --git a/ebuild-functions.tex b/ebuild-functions.tex
index 3935800..ab3ed9c 100644
--- a/ebuild-functions.tex
+++ b/ebuild-functions.tex
@@ -24,7 +24,7 @@ Ebuilds must not call nor assume the existence of any phase functions.
 
 Some functions may assume that their initial working directory is set to a particular location;
 these are noted below. If no initial working directory is mandated, it may be set to anything and
-the ebuild must not rely upon a particular location for it. The ebuild \e{may} assume that the
+the ebuild must not rely upon a particular location for it. The ebuild \emph{may} assume that the
 initial working directory for any phase is a trusted location that may only be written to by a
 privileged user and group.
 
diff --git a/introduction.tex b/introduction.tex
index 8d1f793..b72acc3 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -5,7 +5,7 @@
 This document aims to fully describe the format of an ebuild repository and the ebuilds therein, as
 well as certain aspects of package manager behaviour required to support such a repository.
 
-This document is \e{not} designed to be an introduction to ebuild development. Prior knowledge of
+This document is \emph{not} designed to be an introduction to ebuild development. Prior knowledge of
 ebuild creation and an understanding of how the package management system works is assumed; certain
 less familiar terms are explained in the Glossary in chapter~\ref{ch:glossary}.
 
@@ -28,7 +28,7 @@ incompatibilities with any particular repository.
 \section{Reporting Issues}
 
 Issues (inaccuracies, wording problems, omissions etc.)\ in this document should be reported via
-Gentoo Bugzilla using product \e{Gentoo Hosted Projects}, component \e{PMS/EAPI} and the default
+Gentoo Bugzilla using product \i{Gentoo Hosted Projects}, component \i{PMS/EAPI} and the default
 assignee. There should be one bug per issue, and one issue per bug.
 
 Patches (in \t{git format-patch} form if possible) may be submitted either via Bugzilla or to the
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex
index b807117..59edc1c 100644
--- a/pkg-mgr-commands.tex
+++ b/pkg-mgr-commands.tex
@@ -184,7 +184,7 @@ completing. Ebuilds must not run any of these commands once the current phase fu
     a failure message provided in its first and only argument, and then aborts the build process.
 
     \featurelabel{subshell-die} In EAPIs listed in table~\ref{tab:die-properties} as not providing
-    subshell support, \t{die} is \e{not} guaranteed to work correctly if called from a subshell
+    subshell support, \t{die} is \emph{not} guaranteed to work correctly if called from a subshell
     environment.
 \item[assert] Checks the value of the shell's pipe status variable, and if any component is non-zero
     (indicating failure), calls \t{die}, passing any parameters to it.
@@ -1027,7 +1027,7 @@ has returned.
     \item \featurelabel{unpack-absolute} Otherwise, for EAPIs listed in
         table~\ref{tab:unpack-behaviour} as supporting absolute and relative paths, the argument is
         interpreted as a literal path (absolute, or relative to the working directory); for EAPIs
-        listed as \e{not} supporting such paths, \t{unpack} shall abort the build process.
+        listed as \emph{not} supporting such paths, \t{unpack} shall abort the build process.
     \end{compactitem}
 
     Any unrecognised file format shall be skipped silently. If unpacking a supported file format
diff --git a/pms.cls b/pms.cls
index d7c6ed8..ee0d60f 100644
--- a/pms.cls
+++ b/pms.cls
@@ -110,7 +110,6 @@
     \renewcommand{\i}[1]{\textit{#1}}
     \renewcommand{\t}[1]{\texttt{#1}}
 }
-\newcommand{\e}[1]{\emph{#1}}
 \newcommand{\note}[1]{\begin{trivlist}\item\textbf{Note:} #1\end{trivlist}}
 
 % Because we are lazy, we define a table environment to fulfil our needs
diff --git a/profiles.tex b/profiles.tex
index 76c9278..a3e666e 100644
--- a/profiles.tex
+++ b/profiles.tex
@@ -40,7 +40,7 @@ If a profile contains a file named \t{deprecated}, it is treated as such. The fi
 file should contain the path from the \t{profiles} directory of the repository to a valid profile
 that is the recommended upgrade path from this profile. The remainder of the file can contain any
 text, which may be displayed to users using this profile by the package manager. This file is not
-inherited---profiles which inherit from a deprecated profile are \e{not} deprecated.
+inherited---profiles which inherit from a deprecated profile are \emph{not} deprecated.
 
 This file must not contain comments or make use of line continuations.
 
diff --git a/tree-layout.tex b/tree-layout.tex
index 80d70d6..138e533 100644
--- a/tree-layout.tex
+++ b/tree-layout.tex
@@ -35,7 +35,7 @@ the category. Each category directory shall contain:
 \end{compactitem}
 
 Category directories may contain additional files, whose purpose is not covered by this
-specification. Additional directories that are not for a package may \e{not} be present, to avoid
+specification. Additional directories that are not for a package may \emph{not} be present, to avoid
 conflicts with package name directories; an exception is made for filesystem components whose name
 starts with a dot, which the package manager must ignore, and for any directory named \t{CVS}.
 
@@ -120,7 +120,7 @@ manager must ignore any files in this directory that it does not recognise.
 \item[desc/] This directory contains files analogous to \t{use.desc} for the various \t{USE_EXPAND}
     variables. Each file in it is named \t{<varname>.desc}, where \t{<varname>} is the variable
     name, in lowercase, whose possible values the file describes. The format of each file is as for
-    \t{use.desc}, described in section~\ref{sec:use.desc}. The \t{USE_EXPAND} name is \e{not}
+    \t{use.desc}, described in section~\ref{sec:use.desc}. The \t{USE_EXPAND} name is \emph{not}
     included as a prefix here.
 \item[updates/] This directory is described in section~\ref{sec:updates-dir}.
 \end{description}