Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing documentation for -x in the rx(1) manpage #502

Merged
merged 2 commits into from
Oct 23, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 20 additions & 17 deletions man/rx.1/rx.1.xml
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,7 @@
<!ENTITY v.opt "<option>-v</option>">
<!ENTITY w.opt "<option>-w</option>">
<!ENTITY X.opt "<option>-X</option>">
<!ENTITY x.opt "<option>-x</option>">

<!ENTITY h.opt "<option>-h</option>">
]>
Expand Down Expand Up @@ -403,29 +404,20 @@
<term>&u.opt;</term>

<listitem>
<para>Allow ambiguities.
This means patterns with different ids may match the same text.
The default is to error for conflicts.</para>

<para>It's possible to have multiple patterns with the same id
(i.e. by being in the same file when using multi-file mode),
and these are not considered a conflict because they key
to the same id.</para>
</listitem>
</varlistentry>

<varlistentry>
<term>&u.opt;</term>
<para>Allow ambiguities between patterns.
This means patterns with different ids may match the same text.</para>

<listitem>
<para>Allow ambiguities between regexps,
such that multiple regexps may match the same text.
The default is to error for ambiguities,
<para>The default is to error for ambiguities,
requiring all regexps unioned to be non-overlapping.
Formally, the requirement is that they are disjoint languages.
Erroring for ambiguities applies after multiple regexps are joined,
either by union or by concatenation (&s.opt;).</para>

<para>It's possible to have multiple patterns with the same id
(i.e. by being in the same file when using multi-file mode),
and these are not considered a conflict because they key
to the same id.</para>

<para>&u.opt; is implied by &n.opt;.</para>
</listitem>
</varlistentry>
Expand Down Expand Up @@ -462,6 +454,17 @@
</listitem>
</varlistentry>

<varlistentry>
<term>&x.opt;</term>

<listitem>
<para>Literals are unanchored.
This applies to all literals; for finer control use a regex dialect.
The default is that literals are anchored,
as if written <code>^abc$</code> in regex syntax.</para>
</listitem>
</varlistentry>

<varlistentry>
<term>&h.opt;</term>

Expand Down