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
Greetings!
There are a lot of similar lines in the vscode-esp-idf-extension settings that confuse beginners and greatly annoy more experienced users (e.g., me)
Using the example of typescript, I propose a solution to the problem with different delimiters in the path, depending on the platform on which vscode-esp-idf-extension is running.
import*asosfrom'os';constplatform=os.platform();if((platform==="linux")||(platform==="darwin")){// linux or OS X// e.g.SLASH='/';}elseif(platform==="win32"){// Windows...// e.g.SLASH='\\';}
This will allow to show only the necessary elements in the vscode-esp-idf-extension settings.
The text was updated successfully, but these errors were encountered:
Thank you for this feature request. To make sure I understand your proposal correctly:
Are you suggesting that the extension should automatically detect the platform and:
Only show relevant platform-specific settings in the VS Code settings UI? Or to have different descriptions, so that the user would understand what's the difference between "idf: Build Path" and "idf: Build Path Win" for example?
Automatically handle path delimiter conversion internally (/ vs ) without requiring separate settings for each OS?
Only show relevant platform-specific settings in the VS Code settings UI and automatically handle path delimiter conversion internally (/ vs ) without requiring separate settings for each OS
An acceptable option
Or to have different descriptions, so that the user would understand what's the difference between "idf: Build Path" and "idf: Build Path Win" for example?
This only leads novice users into a stupor from the huge number of almost identical lines. And others will probably wonder why, if everything can be done automatically, without user intervention.
I've been working of ESP chips since 2013. It's my hobby. Until recently for my, the VS Code + PlatformIO bundle was the perfect solution for ESP programming and firmware. From time to time, I installed vscode-esp-idf-extension and tried to work with it. Alas, unsuccessfully.
I tried again a while ago. And I did it. I was even able to set up a multi-project. Good job.
The vscode-esp-idf-extension still has many "childhood illnesses", but now we can say with confidence that the extension has gained momentum and I am happy to contribute to the development of the project.
Greetings!
There are a lot of similar lines in the
vscode-esp-idf-extension
settings that confuse beginners and greatly annoy more experienced users (e.g., me)Using the example of
typescript
, I propose a solution to the problem with different delimiters in the path, depending on the platform on whichvscode-esp-idf-extension
is running.This will allow to show only the necessary elements in the
vscode-esp-idf-extension
settings.The text was updated successfully, but these errors were encountered: