Re: [ide-dev] Implicit editor saving and Auto Building in Eclipse
Bruno, nice to hear this, I'm currently working with Orion and one of the things I like is 'auto-save' which I leave on all the time...
Just a heads up that when looking at implementing this be aware that you are going to have to come up with a strategy that can auto-save *without* losing the ability to refer to / compare changes in the local files (also quite useful). Not sure what the answer is but I don't think simply spamming the current mechanism with tons of saves will be sufficient...
Bruno Medeiros ---11/11/2015 09:32:15 AM---I was considering participating in the FEEP proposal "Implement Auto-Save of Editors" (
From: Bruno Medeiros <bruno.do.medeiros@xxxxxxxxx>
Date: 11/11/2015 09:32 AM
Subject: [ide-dev] Implicit editor saving and Auto Building in Eclipse
Sent by: ide-dev-bounces@xxxxxxxxxxx
I was considering participating in the FEEP proposal "Implement Auto-Save of Editors" ( https://projects.eclipse.org/development_effort/implement-auto-save-editors ), as this is something I was already contemplating contributing to.
However, my interest in this feature is not simply to have an auto-backup of dirty editors, I'd like to be able to entirely remove the concept of explicitly-saving (and of dirty editors as a consequence), but instead implicitly save editors to their original files, not to a temporary copy somewhere else. IntelliJ follows this behavior.
So, I've originally posted about this here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=34076#c89 , but I'd like to bring up this issue with a wider audience that just those listening to the bug. Especially with regards to how this relates to Auto Building, and the question about the usefulness of Auto Building (please see that bugzilla comment).
-- Bruno Medeiros
ide-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit