Jonathan Watt c0331fe643 Bug 1408810 - Get the Eclipse CDT code formatter working again. r=botond ... This makes us write the code formatter settings into the workspace settings directory instead of the project settings directory. This is preferable since when users make settings changes they are more likely to work with the workspace settings, so we should put them there. Putting them there also fixes a bug whereby the calls to _write_noindex/_remove_noindex would overwrite the formatter settings file shortly after it had been created. To get the formatter to show up in the UI we also need to set the formatter settings as a one line pref value in the CDT UI settings. This duplication is what Eclipse does when a new formatter is manually added, and it's necessary to get the formatter working correctly. MozReview-Commit-ID: KP4w0VbNCF7		2017-09-27 19:43:16 +01:00
..
dumbmake	Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester	2016-11-16 09:59:22 -05:00
mozbuild	Bug 1408810 - Get the Eclipse CDT code formatter working again. r=botond	2017-09-27 19:43:16 +01:00
mozpack	Bug 1393242 - Normalize paths in MercurialRevisionFinder; r=mshal	2017-08-31 10:39:28 -07:00
setup.py
TODO