Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Ignored names doesn't accept .* as a valid input (to hide all files beginning with a '.', standard unix philosophy) #1966

Closed
lutzee opened this issue May 6, 2014 · 3 comments

Comments

@lutzee
Copy link

lutzee commented May 6, 2014

Inputting .* into the Ignored Names setting does not read it as a valid wildcard for any files/folders beginning with a .
In unix and things based off/designed around, files and folders beginning with a . are classed as hidden and by default should be hidden by things listing the directories unless they are explicitly told to list the hidden files. I'm not asking for this, but at least a way to achieve this, through the use of .*.

I believe the Ignored Names setting should be accept any form of wildcard, be it *.file, *somefilename* or .*. And currently believe that this is a bug in the system currently implemented.

smashwilson referenced this issue in atom/tree-view May 7, 2014
Supporting all of minimatch's features should be given more thought
and extension ignoring is the common case that really needs initial
support.
@vellerefond
Copy link

I have started work on a project management package called project-ring that supports using a regular expression to hide files/folders in the tree view (at least until this is a tree view built-in feature). You can find more about it here: https://atom.io/packages/project-ring.

@izuzak
Copy link
Contributor

izuzak commented Sep 14, 2015

Seems like this was fixed in the meantime. Here's a GIF where I'm trying out various patterns with * -- notice how the list of files in the tree view changes as I update the ignored names config setting:

ignore

Let me know if you can still reproduce this and please provide an example. Thanks!

@lock
Copy link

lock bot commented Jan 20, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants