Describe the bug
Only version 6 has this bug in both Windows and Linux.
In Linux: when I use open folder and enter a file/folder with a Linux shortcut, I see the vhdl-ls error appear in a different file than the file I'm working on, the errors are mapped to the same file but with the full path, while the file that is shown to me is without errors because the path His is abbreviated.
Even in Windows, when I open a network folder that is mapped to a drive on my computer, I don't see the errors because the file that I open is with the path of the drive, while the errors are mapped to a file with the full path of the network folder.
To Reproduce
Make sure that the path sent to vhdl-ls is the path shown in vscode and not the full path
Please complete the following information:
OS: [linux & windows]
VSCode version 1.88/1.82
Screenshots
Here is the path of the file I opened in vscode
Here, on the other hand, this is the path where the errors of the vhdl-ls are displayed and a file but with a full path (shown as another file in vscode)
Describe the bug Only version 6 has this bug in both Windows and Linux. In Linux: when I use open folder and enter a file/folder with a Linux shortcut, I see the vhdl-ls error appear in a different file than the file I'm working on, the errors are mapped to the same file but with the full path, while the file that is shown to me is without errors because the path His is abbreviated. Even in Windows, when I open a network folder that is mapped to a drive on my computer, I don't see the errors because the file that I open is with the path of the drive, while the errors are mapped to a file with the full path of the network folder.
To Reproduce Make sure that the path sent to vhdl-ls is the path shown in vscode and not the full path
Please complete the following information:
Screenshots Here is the path of the file I opened in vscode
Here, on the other hand, this is the path where the errors of the vhdl-ls are displayed and a file but with a full path (shown as another file in vscode)