Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Absolute paths to custom file icons don't work
See original GitHub issueThis issue was originally mentioned in #984, however I felt it deserves a separate issue.
Specifying absolute paths to file icons, even inside the .vscode/extensions folder does not work. For example, even though the two paths below point to the same file, the first one works while the second one does not.
"material-icon-theme.files.associations": {
"*.pyx": "../../icons/cython", // WORKS
"*.pyx": "C:/Users/[username]/.vscode/extensions/icons/cython" // DOESN'T WORK
}
While this issue does not personally affect me, I’m primarily adding it for the sake of documentation. If this is intended behavior, it should be noted.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@kaleidawave currently I’m not sure about it, absolute paths would be much better, I know. It would be amazing if you could have a look at it 😃
Excellent! Thanks for highlighting the current implementation and its constraints. When I get around to it I will have a look at replacing the string interpolation with some kind of path manipulation and that should allow for absolute icon paths.