-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random CoffeeScript file showing up as Appveyor #563
Comments
Right, kick devtools open. Run this: _FileIcons.fs.paths Tell me if:
Next: const fubar = _FileIcons.grep("git-repository-spec.coffee"); Show me the contents of:
|
The path for The two properties are undefined. |
2017 and Microsoft still insist on using relics of the DOS-era. Christ, I hate those separators... Right, that's made the catalyst pretty clear. What I can't understand is how it fell through the dozens of Thankfully, stuff like this is about to become easier to debug. Almost finished decoupling the filesystem API... -_- Guess there's nothing insightful in |
Oh, all my keys were Windows-style. Their corresponding File was mapped to a Unix-style path though. Is that worrisome? EDIT: As for EDIT2: Found it. The path again is appveyor.yml instead of git-repository-spec.coffee. |
Quite the opposite. To make my life simpler and less prickly, I force Windows paths to use POSIX path separators. Every path is meant to be normalised this way before lookup. Obviously something slipped through the gaps somewhere, because those keys aren't meant to be delimited like that. Is your |
|
The separator discrepancies are the reason for this schizophrenic mess. If I can plug that, this issue will likely be resolved. Needless to say, this is probably connected to the original issue you filed. I should also check the latest beta to see if there's anything broken I need to fix... -_- |
BTW, improved path-handling will need to wait for another release. I didn't wanna hold off publishing Which overlooks the fact I just spent several hours mud-wrestling both NPM and APM to get these versions published, but yeah. |
Just updated to 2.1.1 and I ❤️ the new test icons though :). |
Glad to hear that, haha. Spent hours designing 'em. :) It's interesting how difficult icons are to design well... so little room, so many details can get lost so easily... |
@Alhadis is this maybe the same issue that I'm seeing right now? This is on the freshly-cloned language-csharp repo. |
Freshly-cloned? As in, you didn't create new directories or rename files in the Have you cloned this repo to its current directory before...? |
Could you show the output of |
When you run |
Oh hey, look at this. Want me to file a new issue? Only happened in Window 1 (which is in dev mode).
|
I'm also getting errors from the github package, so maybe it's not just file-icons. |
Are you running a beta version of Atom, or has it been built from master directly? |
I'm running Atom 1.22.0-dev-f762bf954. Should have included that, sorry. |
Can you test this in a stable environment, please? |
Will try to. |
Ok, as this is happening with literally every new repo I'm cloning, I suspect it may be due to my tree-view Map changes. I will attempt to report back soon. |
@50Wliu Don't forget to leverage the filesystem API's index ( I appreciate the time you're putting towards investigating this. |
Right, this should be solved with the latest release. Could you confirm? If not the incorrect icons, then certainly the inconsistent path separators. I've added a speciality class to help deal with that. |
Whoops, missed this. I'll get back to you when I have time. |
I also see this: Atom 1.25.0-dev-3039ac1f4, [email protected]. |
The tab icon when you open it is the Coffeescript brown + the Appveyor icon. Switching languages does not help.
[email protected]
The text was updated successfully, but these errors were encountered: