"Ignored Names" in Preferences has no effect in TreeView

[yalla]

The list of ignored names in the preferences don't have any effect in the TreeView. Letting it to the defaults still shows files/directories like .git, Thumbs.db and the such. Even explicitly defining these has no effect.
Starting atom in safe-mode did not help.
The error is there since I installed it in the first place and I didn't bother to report it until now.

OS: OSX 10.10.5
Atom build: 1.4.3 (official build from website)
Installed additional community packages:

• git-plus
• plantuml-viewer
• vim-mode

I've attached a screenshot. Anything else I need to provide?

Thanks, Alex.

[50Wliu]

Tree View has a separate options "Hide VCS Ignored Files" or something like that which you need to enable in order to hide those files (alternatively, try pressing i while the Tree View is focused). Hope that helps!

[yalla]

You probably mean "Exclude VCS Ignored Paths"? That is also enabled. Pressing "i" didn't help either. I'm kinda lost. It's not like my life depends on it, I'm just wondering if I'm doing something wrong.

[lee-dohm]

He meant "Hide VCS Ignored Files" in the Tree View Settings:

1. Launch Atom 2. Open Settings View with Cmd+, on OS X or Ctrl+, on other platforms 3. Click the Packages tab 4. Search for "tree-view" 5. Click the Settings button in the tree-view package box 6. Check "Hide VCS Ignored Files"

Pressing I probably didn't help because you have to have the Tree View focused before it will work.

[yalla]

@lee-dohm Thanks, that helped, although I also had to check "Hide Ignored Names". "i" didn't work because I don't have a .gitignore file (I guess) in some project directories. I find it a little confusing that the Ignored Names from the Core Settings don't have any effect unless you check the "Hide Ignored Names" in tree-viewer's settings. Thanks for your support!

[lee-dohm]

I'm glad that I was able to help. We agree that this is confusing. We just haven't thought of a better system yet 😆

Thanks for using Atom!

[lock]

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!