"Steinar H. Gunderson" <se...@debian.org> wrote: > It sounds pretty harsh to break a feature used by even the default > configuration.
Iʼm afraid, that Iʼve failed to locate where switches `-n` or `-e` (and command line options at all) are used in the default setup. > I do agree it is problematic not to support pruning filenames with spaces in > them, though; how would you feel about escaping them in the configuration file Well, Iʼm glad, that youʼve asked, as that allows me to highlight a quite minor, yet another UI/UX problem: since configuration file cannot be neither overridden (`--config FILE`) nor disabled entirely (`--no-config`), I actually feel about it like about a missing stair I have to bear in mind. It other words, it would not be much of an issue if updatedb did not support config files at all, and all necessary options were specified in a wrapper script or even directly in systemd-unit / initscript. Even if there is a need for a file (for instance, there are concerns about exceeding the length limit), I believe that inventing (and supporting) a separate format for it does not really worth it. Treating its content as an initial part of command line (with an optional exception of allowing comment lines) simplifies things a lot at least for a user (and I hope for developer too). Thatʼs an approach, that, say, youtube-dl(1) takes. > and then a flag like --add-single-prunepath that does no splitting? If thatʼs a question, whether long options that do no splitting have to be named differently, then yes, sure, as they are explicitly plural now. And presumably just `--add-prunepath` differs enough to be used.
signature.asc
Description: PGP signature
