Add option or instruction in readme how to hide the tree view as a default

[Speldosa]

Prerequisites

• [Since this isn't a bug, I haven't tried these steps] 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

This is a feature request. As of now, the tree view/project pane shows when you open the program. I would like this to be hidden as a default.

Steps to Reproduce

1. Open the program.

Expected behavior: I don't want to see the tree view.

Actual behavior: I see the tree view.

Reproduces how often: 100%

Versions

All of them.

Additional Information

This could either be solved by making it an explicit option or by providing instructions in the readme how to modify the program to do this.

[winstliu]

Thanks for reaching out!

We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.

Thanks for understanding and meeting us half way 😀

[Speldosa]

I updated the thread start.

[Arcanemagus]

Thanks for taking the time to contribute!

We noticed that this is a duplicate of #530. You may want to subscribe there for updates.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.

For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.