Searched refs:offensive (Results 1 – 3 of 3) sorted by relevance
449 char *tpath, *offensive; in add_file() local469 offensive = NULL; in add_file()472 offensive = off_name(path); in add_file()476 path = tpath = offensive; in add_file()477 offensive = NULL; in add_file()495 if (All_forts && offensive != NULL) { in add_file()498 path = tpath = offensive; in add_file()499 offensive = NULL; in add_file()550 do_free(offensive); in add_file()560 all_forts(fp, offensive); in add_file()[all …]
23 Fortunes are split into potentially offensive and not potentially24 offensive parts. The offensive version of a file has the same name as the25 non-offensive version with "-o" concatenated, i.e. "fortunes" is the standard26 fortune database, and "fortunes-o" is the standard offensive database. The28 "-o" is potentially offensive, and should therefore only be displayed if31 Potentially offensive fortune files should NEVER be maintained in33 To create a new, potentially offensive database, use caesar to rotate it,39 MUST be in the potentially offensive database. Fortunes containing any41 potentially offensive database. Political and religious opinions are often42 sequestered in the potentially offensive section as well. Anything which
130141 offensive