I didn't really "jump through hoops". I just did what I would do on Linux...I searched for the Linux files. Found the Linux files. Started working with the Linux files. Turns out, that's a bad idea. Files disappeared.
I've seen numerous reports of other folks entire Linux filesystem being corrupted beyond use. So, I'm not alone in doing this...and (at the time) the docs had a single (non-threatening) sentence about it, when I went back to see if maybe I'd missed something. It basically said something along the lines of "this doesn't work", rather than "this will destroy your files".
It's not a big deal. It was bleeding edge stuff when I started playing with it; things go wrong, and I expect things to go wrong when I'm on the bleeding edge. I like where they're going.
But, it's a thing to be aware of. I wasn't aware of it, based on the docs I read on the subject, so I mentioned it, just in case someone else might not be aware of it.
The thing is, I'm not a Windows user; things that may seem obvious to a Windows user (like, "those files aren't obviously visible for a reason and that reason is don't touch them!") are not always obvious to me.
Then again, you're not the first person to say the files are "hidden"; but I was able to find them, probably using the "find" command in the git or cygwin bash shell, or something (I dunno what else I'd use to find them), but maybe using system search. I don't remember...it wasn't a momentous occasion. I just wanted to edit some files in Atom, so I went and found the files I wanted to edit, using some tool on the system. Again, I don't know Windows. If the state of these files was somehow telling me not to touch them, I did not pick up that signal.
I've seen numerous reports of other folks entire Linux filesystem being corrupted beyond use. So, I'm not alone in doing this...and (at the time) the docs had a single (non-threatening) sentence about it, when I went back to see if maybe I'd missed something. It basically said something along the lines of "this doesn't work", rather than "this will destroy your files".
It's not a big deal. It was bleeding edge stuff when I started playing with it; things go wrong, and I expect things to go wrong when I'm on the bleeding edge. I like where they're going.
But, it's a thing to be aware of. I wasn't aware of it, based on the docs I read on the subject, so I mentioned it, just in case someone else might not be aware of it.
The thing is, I'm not a Windows user; things that may seem obvious to a Windows user (like, "those files aren't obviously visible for a reason and that reason is don't touch them!") are not always obvious to me.
Then again, you're not the first person to say the files are "hidden"; but I was able to find them, probably using the "find" command in the git or cygwin bash shell, or something (I dunno what else I'd use to find them), but maybe using system search. I don't remember...it wasn't a momentous occasion. I just wanted to edit some files in Atom, so I went and found the files I wanted to edit, using some tool on the system. Again, I don't know Windows. If the state of these files was somehow telling me not to touch them, I did not pick up that signal.