Searched refs:offensive (Results 1 – 4 of 4) sorted by relevance
| /freebsd/usr.bin/fortune/fortune/ |
| H A D | fortune.c | 447 char *tpath, *offensive; in add_file() local
467 offensive = NULL; in add_file()
470 offensive = off_name(path); in add_file()
474 path = tpath = offensive; in add_file()
475 offensive = NULL; in add_file()
493 if (All_forts && offensive != NULL) { in add_file()
496 path = tpath = offensive; in add_file()
497 offensive = NULL; in add_file()
548 do_free(offensive); in add_file()
558 all_forts(fp, offensive); in add_file()
[all …]
|
| /freebsd/usr.bin/fortune/ |
| H A D | Notes | 23 Fortunes are split into potentially offensive and not potentially
24 offensive parts. The offensive version of a file has the same name as the
25 non-offensive version with "-o" concatenated, i.e. "fortunes" is the standard
26 fortune database, and "fortunes-o" is the standard offensive database. The
28 "-o" is potentially offensive, and should therefore only be displayed if
31 Potentially offensive fortune files should NEVER be maintained in
33 To create a new, potentially offensive database, use caesar to rotate it,
39 MUST be in the potentially offensive database. Fortunes containing any
41 potentially offensive database. Political and religious opinions are often
42 sequestered in the potentially offensive section as well. Anything which
|
| /freebsd/contrib/pkgconf/ |
| H A D | CODE_OF_CONDUCT.md | 10 to engage in discriminatory, disparaging or offensive speech or actions,
|
| /freebsd/share/dict/ |
| H A D | web2 | 130141 offensive
|