.Dd $Mdocdate: September 22 2015 $
.Dt EEPROM 8
.Os
.Sh NAME
.Nm eeprom
.Nd display or modify contents of the EEPROM or OpenPROM
.Sh SYNOPSIS
.Nm eeprom
.Op Fl cipv
.Op Fl f Ar device
.Op Fl N Ar system
.Oo
.Ar field Ns Op = Ns Ar value
.Ar ...
.Oc
.Sh DESCRIPTION
Observe the following details:
.Bl -dash
.It
Both
.Ar field
and
.Ar value
are marked up with
.Ic \&Ar
because they need to be replaced by the user.
.It
From the user's perspective, the equal sign is considered as
punctuation, so it doesn't need semantic markup.
It doesn't need physical markup either because right after the
.Ic \&Op
macro, normal font mode is active, anyway.
.It
From the technical perspective of the
.Xr mdoc 7
language, the equal sign is not considered as punctuation, but as
a normal character; so it doesn't need to be escaped.
.It
Spacing needs to be suppressed both after the field and before the value.
.It
There is no need to suppress spacing before the equal sign because
right after the opening of an enclosure, in this case right after
.Ic \&Op ,
no spacing is generated in the first place.
.It
.Ic \&Ar Ar ...
is used to indicate that the previous argument may be repeated.
.It
There is a nested enclosure with the outer enlosure containing
additional content after the end of the inner enclosure.
In that case, implicit enclosures (those extending to the end
of the line) don't do the job.
At least one of the enclosures needs to be explicit, that is,
have an end macro.
The solution above chose to make the outer enclosure explicit,
letting it span multiple lines.
In simple cases, one can alternatively make the inner enclosure
explicit and put everything on one input line as follows:
.Pp
.D1 Op Ar field Ns Oo = Ns Ar value Oc Ar ...
.El