or new file and then copy-paste) they just editing existing file with idea of using "Save As" later or just cancel/undo all changes on close. editing wrong files (by mistake or on purpose) - instead of creating new file which is similar to already existing one (via copy.maybe because quite a lot of people have some habits influenced by no-auto-save-available software (in this particular case), e.g. "In communist Russia, the IDE saves the file for you" In IDE Settings -> Editor -> Editor tabs, check "Mark modified tabs with asterisk". This is the maximum number of seconds that the autosave function can be disabled for, and I have absolutely no idea whatsoever why JetBrains picked this weird number.ΔΆ. If it's greyed out, set it to 6442450 seconds (about 74 days). if you can, uncheck "Save files if application is idle for".uncheck "Save files on frame deactivation".uncheck "Synchronize files on frame activation".The problem is that with Webstorm's auto-saving, meteor would push changes way too often, frequently causing compile errors on the server side Node.JS, and sometimes breaking the server. I develop with meteor, which is an awesome web framework that supports live hot code pushes - that is, when a file in the project is updated, the meteor server updates the client, live - you don't even have to tell your users to refresh the page.
0 Comments
Leave a Reply. |