Eclipse code formatter on save12/27/2023 ![]() > It's not important only for me but there are a lot of people out there However I'm a developer but I don't know the Eclipse code, if I can help I'll do. I know it's an open source project but if to close this report the project needs six or more years maybe there is really something wrong. It's not important only for me but there are a lot of people out there waiting for this feature and I think six years are enough. > project committers are fairly prompt in reviewing posted patches. > If it's important for you to have this fixed, you're welcome to pick up the > review comments, but the original author of the patch doesn't have the time > comment 7, it has been reviewed, it needs to be revised to address the > The current status of this bug is that there is a patch posted for review in > to work on specific features needed by their employer. The handful of people who are paid to work on it are paid > Most of the people contributing to Eclipse do so in their spare time on a > of which you can make demands as a customer. > Eclipse is an open-source project there is no commercial company behind it ![]() (In reply to Nathan Ridge from comment #9) As you can see from the review, the project committers are fairly prompt in reviewing posted patches. If it's important for you to have this fixed, you're welcome to pick up the work and make the revisions yourself. The current status of this bug is that there is a patch posted for review in comment 7, it has been reviewed, it needs to be revised to address the review comments, but the original author of the patch doesn't have the time to do so. The handful of people who are paid to work on it are paid to work on specific features needed by their employer. Most of the people contributing to Eclipse do so in their spare time on a volunteer basis. Fix and close this bug report ASAP.Įclipse is an open-source project there is no commercial company behind it of which you can make demands as a customer. > A bug opened in 2008 and still open? Wow. I suppose it shouldn't be too hard to emulate a "Ctrl+Shift+F" keystroke on editor-open notification of selected file types (eg C/C++ files only)? At least it should be easier than format-on-save which always bears some risk of saving (and committing) formatting changes that have never been reviewed ? If I don't like the auto-formatting for any reason, I simply choose "Undo" and the auto-formatting changes are all gone. This has some advantages like providing auto-formatted code for better readability, and giving me the option of reviewing the formatting before actually saving. I've found that the commercial "JIndent" solution supports a "format-on-open" Preference, which formats the source code when a file is opened in the editor (see attached screenshot). StackOverflow discusses the lack of this feature here: Screenshot of JIndent "Format on Open" Preference
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |