setfont: Order of command-line arguments changed with kbd 2.7 #122
Description
Hello!
I am not sure if this is intentional, but the rewrite of the command-line argument parser (included with kbd 2.7) seems to have changed the order in which command-line arguments can be supplied. Previously (i.e. prior to kbd 2.7), certain parameters (such as -C) had to be passed after the font name. For example:
setfont my-fancy-font.psf.gz -C /dev/tty1
However, with kbd 2.7 this results in the following error message:
setfont: Unable to find file: -C
This breaks software such as OpenRC which passes -C after the font name. Why does OpenRC do that? Because the SYNOPSIS section in the setfont(8) man page recommends it:
SYNOPSIS
setfont [-O font+umap.orig] [-o font.orig] [-om cmap.orig] [-ou
umap.orig] [-N] [font.new ...] [-m cmap] [-u umap] [-C console] [-hH]
[-f] [-v] [-V]
This is still the case for the setfont man page in kbd-2.7. Hence, I am opening this issue to figure out: Whether this is this a documentation issue (i.e. the setfont(8) man page needs to be updated) or if the regression in the argument parser is unintentional (i.e. its a bug in the code and we shouldn't update OpenRC and other users of setfont).