| Summary: | The ".orion" folder should (probably) be hidden | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | Node | Assignee: | Michael Rennie <Michael_Rennie> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P4 | CC: | Carolyn_MacLeod, mamacdon, Silenio_Quarti, steve_northover |
| Version: | 12.0 | ||
| Target Milestone: | 15.0 | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Michael Rennie
Personally I like having that stuff visible, it makes the server preferences feel less magical and gives you an easy way to import settings from another orion, or recover from a bad pref state. But YMMV I think (?) devs generally know that dot-files are for configuration, and they're "use at your own risk", so you'd better know what you are doing before editing one. However, what I don't know is how robust other apps are that rely on dot-files. For example, if someone edited a .cshrc or .login file in Linux/Unix and they put bogus stuff in there, would they destroy their ability to log in or run their c shell? Maybe it should be (yet another) setting? I personally also like seeing config files. My only reason for filing the bug was to ask if this was intentional, and if not, did we want to give users enough rope to (possibly) hang themselves. Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html Now that we have the ability to filter resources, this can be easily fixed. My feeling is leave it visible. Like Car says, dev's know not to touch this stuff. |