The global search function does not find search terms that must be in the project. Under SES I could simply do a global search and instantly find the definition of an object. I have tried setting "files to include" to *.*, nothing in files to exclude, etc. Specific case at hand is that I need to find the definition of BT_UUID_NUS_VAL in the Multi-NUS-Master example project, but I need to /learn how to "drive" the search function for future use.
So I think I found out where the confusion is from. The project you are referring to is the Multi-NUS-Master example project, this is not part of the official nRF Connect SDK(NCS).
Just to clear up what i meant in the previus comment:
I was thinking that you where using one of our sample in the SDK, so when you are using our nRF connect for desktop and the toolchain manager you select the tag you are on, I just used the latest. 
Clicking on the Open in VS code will open the entire SDK directory in VS code, this is what I call the NCS folder since the path is often called C:\nsc\vX.X.X , sorry for the confusion there.
With VS code now open you can click on the search button or ctrl + shift +F and look for BT_UUID_VAL
This is for tag v1.9.1
Looks like the sample is built of rom the NCS v1.4.1
As for the project you are working with, we would need to add it to the workspace if we want to search. Should be possible to unzip the project in the NCS v1.4.1 directory, could try nrf>samples>, and we can add it with the nRF connect for VS code plugin. 
Seems to work, 
I dont see a BT_UUID_NUS_VAL in the Multi-NUS-Master example project.
Sorry for the misunderstanding hope this clears things up.
So I think I found out where the confusion is from. The project you are referring to is the Multi-NUS-Master example project, this is not part of the official nRF Connect SDK(NCS).
Just to clear up what i meant in the previus comment:
I was thinking that you where using one of our sample in the SDK, so when you are using our nRF connect for desktop and the toolchain manager you select the tag you are on, I just used the latest.
Clicking on the Open in VS code will open the entire SDK directory in VS code, this is what I call the NCS folder since the path is often called C:\nsc\vX.X.X , sorry for the confusion there.
With VS code now open you can click on the search button or ctrl + shift +F and look for BT_UUID_VAL
This is for tag v1.9.1
Looks like the sample is built of rom the NCS v1.4.1
As for the project you are working with, we would need to add it to the workspace if we want to search. Should be possible to unzip the project in the NCS v1.4.1 directory, could try nrf>samples>, and we can add it with the nRF connect for VS code plugin.
Seems to work,
I dont see a BT_UUID_NUS_VAL in the Multi-NUS-Master example project.
Sorry for the misunderstanding hope this clears things up.
