User forums > Nightly builds

The 13 August 2022 build (12864) is out.

<< < (8/15) > >>

MaxGaspa:
@pecan

Just attaching the aaaa project

Max

MaxGaspa:
@pecan

I think I fixed the issue I had with your plugin. I discovered that I had a disk issue saving to the temporary folders. After a scandisk and deleting (forcing) the temp directory and using a new one the observed issue disappeared.  So it seems that the errors saving in the temp directory caused the issue.

Now your plugin is working (well !) and also the crashes i had in the past with a previous version are disappeared.

Max

Pecan:

--- Quote from: MaxGaspa on August 19, 2022, 03:51:32 pm ---@pecan

Just attaching the aaaa project

Max

--- End quote ---

Your aaaa project work perfectly on the latest CB nightly, here on my wx3.1.7 installation.

I suspect that the auto detect of clangd.exe is incorrect.
From the base of your msys64 install, using a command windows, issue the command "dir /s clangd*"

You'll probably find that you have two clangd.exe modules.
Like:

--- Code: ---F:\user\programs\msys64_13.0.1>dir /s clangd*
 Volume in drive F is HPHD2
 Volume Serial Number is 0873-0556

 Directory of F:\user\programs\msys64_13.0.1\clang64\bin

02/04/2022  11:50 AM        14,887,424 clangd.exe
               1 File(s)     14,887,424 bytes

 Directory of F:\user\programs\msys64_13.0.1\mingw64\bin

02/04/2022  11:49 AM        12,204,466 clangd.exe
               1 File(s)     12,204,466 bytes

--- End code ---

Note that there's one clangd.exe in mingw64\bin
and another in clang64\bin.

Look into Setting/Editor/Clangd_client/ tab C/C++ Parser at the entry "Specify Clangd executable to use" and make sure it's set to your directory of mingw64/bin/clangd.exe

MaxGaspa:

--- Quote from: Pecan on August 19, 2022, 08:58:06 pm ---
Your aaaa project work perfectly on the latest CB nightly, here on my wx3.1.7 installation.

I suspect that the auto detect of clangd.exe is incorrect.
From the base of your msys64 install, using a command windows, issue the command "dir /s clangd*"

You'll probably find that you have two clangd.exe modules.

--- End quote ---

I have just one clangd.exe in mingw64 but, as I reported the issue was related to some problems writing to the temp directory. I apologize for the time waste but I discovered the disk issue after  posting the messages (and I discovered it because another application was complaining...)

Now I'd like to know if I have discovered a bug or a feature.

Using a large project it is useful to reduce the symbol browser to show the current file symbols only. But switching from "Current Project's symbols" to "Current file's symbols" no changes in the symbol browser happens. See images. Moreover the namespace is not expanded regardless the setting "Automatically expand namespaces".

Great work anyway !!!!

 

Pecan:
Partial quote

--- Quote from: MaxGaspa on August 19, 2022, 09:33:57 pm ---Now I'd like to know if I have discovered a bug or a feature.

Using a large project it is useful to reduce the symbol browser to show the current file symbols only. But switching from "Current Project's symbols" to "Current file's symbols" no changes in the symbol browser happens. See images. Moreover the namespace is not expanded regardless the setting "Automatically expand namespaces".

--- End quote ---

@MaxGaspa, thanks for testing and thanks for the input.

Unfortunately I've not had the time to pay much attention to the Symbol browser. I hope to do so some time in the future when clangd_client core code runs sucessfully for one month without need of serious fixing.

I've entered the missing features (as you've noted) into the clang_client ticket system so they won't get lost.

Does it help to view/expand the namespace name instead (see attatched image) ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version