<commit_before>.TH ALI %manext1% "December 4, 2013" "%nmhversion%"
.\"
.\" %nmhwarning%
.\"
.SH NAME
ali \- list mail aliases
.SH SYNOPSIS
.HP 5
.na
.B ali
.RB [ \-help ] 
.RB [ \-version ]
.RB [ \-alias
.IR aliasfile ]
.RB [ \-list " | " \-nolist ]
.RB [ \-user " | " \-nouser ]
.RI [ aliases " ...]"
.ad
.SH DESCRIPTION
.B ali
searches the named mail alias files for each of the given
.IR aliases .
It creates a list of addresses for those
.IR aliases ,
and writes that list on standard output.  If no arguments are given,
.B ali
outputs all alias entries.
.PP
By default, when an aliases expands to multiple addresses, the addresses
are separated by commas and printed on as few lines as possible.  If the
.B \-list
option is specified, then when an address expands to multiple
addresses, each address will appear on a separate line.
.PP
The switch
.B \-user
directs
.B ali
to perform its processing in
an inverted fashion: instead of listing the addresses that each given
alias expands to,
.B ali
will list the aliases that expand to each
given address.
.PP
The files specified by the profile entry
.RI \*(lq Aliasfile \*(rq
and any additional alias files given by the
.B \-alias
.I aliasfile
switch will be read.  Each
.I alias
is processed as described in
.IR mh\-alias (5).
.SH FILES
Alias files are looked up in multiple locations: if the pathname is
absolute or starts with
.RI \*(lq . \*(rq
or
.RI \*(lq .. \*(rq
then it's accessed directly; otherwise tilde expansion is done on
usernames, then files are searched for in the user's
.I Mail
directory as specified in their profile.  If not found there, the directory
.RI \*(lq %nmhetcdir% \*(rq
is checked.
.PP
.TP 20<commit_msg>Changes to ali.man<commit_after>.TH ALI %manext1% "December 13, 2016" "%nmhversion%"
.\"
.\" %nmhwarning%
.\"
.SH NAME
ali \- list mail aliases
.SH SYNOPSIS
.HP 5
.na
.B ali
.RB [ \-help ] 
.RB [ \-version ]
.RB [ \-alias
.IR aliasfile ]
.RB [ \-list " | " \-nolist ]
.RB [ \-user " | " \-nouser ]
.RI [ aliases " ...]"
.ad
.SH DESCRIPTION
.B ali
searches the named mail alias files for each of the given
.IR aliases .
It creates a list of addresses for those
.IR aliases ,
and writes that list on standard output.  If no arguments are given,
.B ali
outputs all alias entries.
.PP
By default, when an alias expands to multiple addresses, the addresses
are separated by commas and printed on as few lines as possible.  If the
.B \-list
switch is specified, and an address expands to multiple
addresses, each address will appear on a separate line.
.PP
The
.B \-user
switch directs
.B ali
to perform its processing in
an inverted fashion: instead of listing the addresses that each given
alias expands to,
.B ali
will list the aliases that expand to each
given address.
.PP
The files specified by the profile entry
.RI \*(lq Aliasfile \*(rq
and any additional alias files given by the
.B \-alias
.I aliasfile
switch will be read.  Each
.I alias
is processed as described in
.IR mh\-alias (5).
.SH FILES
Alias files are looked up in multiple locations: if the pathname is
absolute or starts with
.RI \*(lq . \*(rq
or
.RI \*(lq .. \*(rq
it is accessed directly; otherwise tilde expansion is done on
usernames, then files are searched for in the user's
.I Mail
directory as specified in their profile.  If not found there, the directory
.RI \*(lq %nmhetcdir% \*(rq
is checked.
.PP
.TP 20
{'fraction_non_alphanumeric': 0.09673590504451039, 'fraction_numerical': 0.006231454005934718, 'mean_word_length': 3.219023779724656, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '285579', 'n_tokens_mistral': 1122, 'n_tokens_neox': 1048, 'n_words': 550}