Conversation
|
|
||
| - if the fragment came from a project directory, the path is relative | ||
| - if the fragment came from a project directory, the path is relative | ||
| (note: `./dir/.*` is an incorrect form for `dir` content in the project's root |
There was a problem hiding this comment.
I have trouble understanding this sentence (not sure what the "regex perspective" refers to). And listing incorrect examples can add extra confusion. Could this be:
(e.g. for
/proj/.clangd, the file/proj/x/y.cchas a path ofx/y.cc)
There was a problem hiding this comment.
Looks like I misunderstood @HighCommander4 explanation.
It's a common practice to start a path with ./ talking about relative paths. But the config parser doesn't understand that form, it requires starting away with the name, right?
"regex perspective" is my wrong explanation because regex with . special character can be any character including ., so according to my logic, it should have worked. Forget it.
Yeah, your example looks better in every sense.
2 participants
I've added path usage example as discussed with @HighCommander4 here.
The page fragment: