Easier support for custom file extensions about pss HOT 4 CLOSED

I think #4 offers a more generic approach to this, no?

from pss.

#4 is definitely similar and solves the problem to "add these custom files into a list of files that pss looks by default" that I mentioned in the end of the description. It doesn't make it much easier to restrict search only to certain custom extension. Compare these possibilities:

pss -aG '.*\.robot' pattern                    # works now
pss -E robot pattern                           # proposed by this issue
pss --type-add robot=.robot --robot pattern    # proposed by issue #4

I'd probably keep on using the first option even if #4 was implemented because using it so verbose. Needing to type robot three times is a bit too much.

from pss.

I think I already laid this philosophy down somewhere, but can't find it now, so I'll repeat at least partially: it is not my goal to build any option under the sun into pss. Anyone who's looked at its code noticed that the flag parsing code is already super complicated because of the sheer amount of options supported.

I personally have wrapper scripts around pss that just invoke it with extra arguments for special situations - I think this can work for anyone. Then verbosity is not a real problem. In this respect the --type-add proposal is superior because if your pss wrapper actually calls:

pss --type-add robot=.robot "$@"

Then you have your enhanced pss, all the rest works just fine.

What I could consider (I remember someone proposed implementing it but then lost interest) is supporting configuration files that would make specifying lots of options easier. pss could then be pointed to such configuration files, so you'd have:

 pss --config <my_pss_config> $@

In your wrapper script. Or multiple wrapper scripts with multiple configs.

from pss.

Fair enough.

from pss.