Set up indexer and "mark occurrences" prefs appropriately when generating Eclipse CDT project
Categories
(Developer Infrastructure :: Developer Environment Integration, defect)
Tracking
(firefox62 fixed)
Tracking | Status | |
---|---|---|
firefox62 | --- | fixed |
People
(Reporter: botond, Assigned: botond)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 3•6 years ago
|
||
mozreview-review |
Comment 4•6 years ago
|
||
mozreview-review |
Comment 6•6 years ago
|
||
bugherder |
Comment 7•6 years ago
|
||
Botond, does the addition of the indexer.updatePolicy=0
actually work for you? If I remove the eclipse output dir and regenerate the project, indexing does not happen for me when I open it.
Annoyingly I haven't been able to figure out a way to have both the _import_project step not index, and have the project index the first time it's opened by the user after mach build-backend -b CppEclipse
.
Assignee | ||
Comment 8•6 years ago
|
||
(In reply to Jonathan Watt [:jwatt] from comment #7)
Botond, does the addition of the
indexer.updatePolicy=0
actually work for you? If I remove the eclipse output dir and regenerate the project, indexing does not happen for me when I open it.
For me, indexing does happen when I open the project (as far as I can remember).
indexer.updatePolicy
is about whether incremental indexing happens automatically in response to file changes (so e.g. whether an edit to a header file will trigger an index update so that the .cpp file reflects the change).
Now that you mention it, the addition of indexer.updatePolicy=0
has not been having the intended effect for me, but I haven't had time to investigate why.
Updated•2 years ago
|
Description
•