Unable to specify complex path patterns for matching file/directory

[ssbarnea]

Prerequisites

• [x ] Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

As a power user I expect to be able to specify complex patterns for matching file/directories in Atom.

Steps to Reproduce

I tried foo/**/bar/** and foo/.*/bar/.* and I realised that none of them work.

Expected behavior:

Be able to respect the java style globing pattern which allows the first example. Have it documented in the sample text so user will learn how to use without having to read the documentation.

Actual behavior: Anything after ** is ignored so more files are found than expected.

Reproduces how often: Always

Versions

Atom    : 1.23.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0
apm  1.18.11
npm  3.10.10
node 6.9.5 x64
atom 1.23.1
python 2.7.14
git 2.15.0

Additional Information

I do not have a strong preference upon the syntax being supported, which ever is easier to implement but the default example text should contain an example that explains it.

[50Wliu]

We use minimatch for glob matching. I am unaware if minimatch offers what you are looking for.

[y-a-v-a]

Had the same question. This might be of some help:

minimatch('basedir/projectcore/test/script.js', 'basedir/project+(core|)/**/*.js'); // true
minimatch('basedir/projectcore/test/script.js', '**/project+(core|)/**/*.js'); // true
minimatch('basedir/projectcore/test/script.js', '**/project*/**/*.js'); // true
minimatch('basedir/project/test/script.js', 'basedir/project+(core|)/**/*.js'); // true

// globstar not allowed in combination with string
minimatch('basedir/projectcore/test/script.js', '**/project*/**.js'); // false
minimatch('basedir/projectcore/test/script.js', '**/projectcore/**.js'); // false

[jrial]

This probably explains: https://github.com/isaacs/minimatch/issues/67

Seems it won't be fixed, unless someone comes up with a good PR. It looks like yarn has moved to micromatch for this specific reason: https://github.com/yarnpkg/yarn/pull/3339 - although what other issues that might introduce I have no clue about.