Actual behaviour

When simply trying to edit some additional files I often type :e *.js or something similar; this almost ALWAYS results in E77: Too many file names.

Expected behaviour

It's pretty clear what the user wants in this situation; they want to open the files as buffers! I'm sure there are legacy reasons for this error, but it's a pretty poor experience these days that

For different use cases, like bencheeorg/benchee_html#10 it'd be great to have statistics about statistics - what I'd call "meta statistics" - although there's probably some better real statistics name for this :)

What should be in there (that I know of so far):

• job size (how many jobs are in there)
• minimum of run times over all jobs
• maximum of run times over all jobs

This should be

https://github.com/Pext/Pext/blob/master/docs/installation.rst contains instructions for openSUSE, but more repositories are available (despite being untested).

These need to be documented for the relevant distributions:
Stable: https://download.opensuse.org/repositories/home:/TheLastProject:/python-pext/
Nightly: https://download.opensuse.org/repositories/home:/TheLastProject:/python-pext:/d

Backreferences referencing a (named) capture group declared after the reference always expand to an empty string. They are in fact forwardreferences.

/^\1(.)$/.test('aa'); // doesn't match
/^\k<name>(?<name>.)$/.test('a'); // matches only a single character

Related: #615

• Do you want to request a feature or report a bug?
  This issue corresponds to a need for standardization of existing CSV exports in PowSyBl.

• What is the current behavior?
  At the moment, the CSV exports are done with different standards: the separators can be imposed to "," or ";", or taken from the locale set of variables (care must then be taken in the tests to specify the s