I am sure this is a familiar problem, even though I have not found my exact scenario through searches.
Basically, every few hours or so, Atom boycotts one of my files from the remote ftp editor. I click to open, Atom doesn’t care how I click, even if I click REALLY HARD, click to open another file no problem, back to the banned-by-Atom file, it is a no-way-Julius-situation. That file is in one of Al Gore’s boxes, LOCKED.
I am very pleased to report that Atom’s FANTASTIC SPEED at shutting down and restarting make this a tolerable problem. If this were Eclipse or Visual Studio, it would be gouge-out-my-eyes-time.
My primary concern with this issue is I think it must reflect a serious problem that is going to be hard to resolve. I have reason to believe the integrity of Atom’s buffer/cache/memory management has been the subject of extensive consideration, much of it devoted to the exact issue of guaranteeing the integrity of the buffer/cache/memory management. The fact this problem pops up has me thinking making that part of Atom work perfectly might be like building the World Trade Center with cooked spaghetti.
On that note, I gotta tell you. given the speed at which our computers run these days, and the availability of RAM enough to run all code from all the systems I ever worked on all loaded memory,
Sometimes I think browser developers, like those at FireFox/Mozilla, Opera. Safari. you name it those systems have more work put into cache management than makes sense – this is just my suspicion unencumbered by knowledge. When browsers were really new, like in 1995, that was when normal people first learned about cache. Most of what was learned was not the benefit or goal, but rather how to clear it to solve problems it caused. The benefit we were getting was we could save bandwidth. That is a good thing, even great if you are running in a terrible internet connection. But when you have solid fast connection, like cities where most people live, by the time you factor in all the work it takes to make complicated cache work
Is this related to Atom unable to open a file without restart? Picture below with a specific case.
AFTER THE RETART