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’ve recently installed the latest version of Espressif-IDE (v3.0.0):
Version: 3.0.0
Build id: 20240605-1941
In my project, I’m using Windows junctions for certain directories. Everything worked fine with previous versions (e.g., 2.8.1), but with v3.0.0, it’s become difficult to develop code using junctions.
Here are the main issues I’m encountering:
1. File Path Inconsistencies:
When opening a file from the Project Explorer, the junction path is used:
But when opening a file via the indexer (Ctrl + Click), the file is opened using its absolute path:
This results in two different instances of the same file in the IDE, making it easy to lose changes when editing them simultaneously.
2. Debugging Issues:
Breakpoints can only be set on files opened via the junction path, not the file opened by the indexer (the “real” absolute path).
Is this a known problem? Is there a workaround?
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Espressif-IDE (v3.0.0) can not handle Windows Junctions properly
Espressif-IDE (v3.0.0) can not handle Windows Junctions properly (IEP-1339)
Oct 8, 2024
I’ve recently installed the latest version of Espressif-IDE (v3.0.0):
In my project, I’m using Windows junctions for certain directories. Everything worked fine with previous versions (e.g., 2.8.1), but with v3.0.0, it’s become difficult to develop code using junctions.
Here are the main issues I’m encountering:
1. File Path Inconsistencies:
When opening a file from the Project Explorer, the junction path is used:
But when opening a file via the indexer (Ctrl + Click), the file is opened using its absolute path:
This results in two different instances of the same file in the IDE, making it easy to lose changes when editing them simultaneously.
2. Debugging Issues:
Breakpoints can only be set on files opened via the junction path, not the file opened by the indexer (the “real” absolute path).
Is this a known problem? Is there a workaround?
The text was updated successfully, but these errors were encountered: