You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an extension which provides some language support (folding and highlighting) for file trees. When opening an untitled file and pasting in a tree, the extension will try to set the language to tree if it has some specific characters (ex. ├──, └──). However, once language detection kicks in it automatically changes it to ini.
I was testing the language detection code and can clearly see that for a tree file it somehow detects ini with 100% confidence. So there are 2 questions:
Is it a bug that this is being detected as an ini file?
Is there any process for hooking into/add languages to the custom detection API?
I tested the language detection code with the below
I have an extension which provides some language support (folding and highlighting) for file trees. When opening an untitled file and pasting in a tree, the extension will try to set the language to
tree
if it has some specific characters (ex.├──
,└──
). However, once language detection kicks in it automatically changes it toini
.I was testing the language detection code and can clearly see that for a
tree
file it somehow detectsini
with 100% confidence. So there are 2 questions:ini
file?I tested the language detection code with the below
Output:
The text was updated successfully, but these errors were encountered: