autosave

How do I prevent Emacs from creating backup copies of buffers I don't wish to save when I kill buffers that have not been saved? kjfletch See Here Short version: put (setq make-backup-files nil) in you .emacs file, or toggle this feature at any time with M-x auto-save-mode . Here is the Emacs Manual Node. If you don't want emacs to litter your drive with backup files try adding the following to your .emacs file: (setq backup-directory-alist '(("." . "~/emacs-backups"))) This will store every backup in a single location. I would advice you to use something like: (defvar backup-dir "~/.emacs.d

Sometime around May 2014 Notepad++ had an update where it started saving unsaved documents without being told to. When closing Notepad++ it no longer asks whether or not you want to save or discard unsaved documents and instead just closes. When Notepad++ is opened back up the unsaved documents are there still, as before, listed as New 1; New 2; New 3; etc. It looks like it is automatically saving them somewhere when it gets closed. How do you turn this off, so that unsaved documents must either be discarded or saved when you close Notepad++? How do you restore the old behaviour? Zell Faze

I have a posts controller on a small test website I'm making. I want to have a 'save draft'/combo-auto-save function to the site, as the site will have long posts that users may want to leave and come back to finish. However, I've never built an autosave/save function into a Rails app before (or any app). What is a good, RESTful way to do so? Here is my current controller action: posts_controller.rb def create @post = params[:post] if @post.save flash.now[:success] = "Post created!" else render_errors_now(@post) end respond_to do |format| format.html {redirect_to Discussion.find(session[

I would like Eclipse to automatically save every time I edit a file, in much the same way that it builds automatically. Because I've been using IntelliJ for the last year (which saves automatically by default), I keep having the following problem: Make some changes in Eclipse Forget to press save Run the build, unit tests, and notice some strange behaviour (Some time later....) realize that the unexpected behaviour occurred because I forgot to save the changes Is there any way I can make Eclipse save automatically? Eclipse Neon (4.6) Window > Preferences General > Editors > Autosave > check

Coming from a Visual Studio background... How do I tell Eclipse that it should auto save when ever I build rather than ask each time. VS.NET has it under "Options", but I can't find it in Eclipse. I use a Mac. Matschie Go to Window -> Preferences -> General -> Workspace and there you can check: Save automatically before build + Build automatically First, try Window -> Preferences -> General -> Workspace. There you can check "Save automatically before build" and "Build automatically." If that does not work, PLEASE TRY Preferences -> Run/Debug -> Launching -> "Save dirty editors before launching

I'm trying to restore a document based application from a previous version on Lion. When I select "restore version", the text view doesn't reflect the changes. However, if I close the application and reopen, the changes are there. I'm using the file wrapper variants of NSDocument, so how can I make the text view's text storage reflect the version that's selected immediately? Am I missing something? I had a similar problem recently (my interface didn't seem to update). Are you updating your interface in windowControllerDidLoadNib: or awakeFromNib ? When a document is reverted (revert to last

Chrome developer tools has an option to Start/Stop Recording profiling data with respect to Memory,Paint,Screenshots,JS Profile on the Timeline tab. Once I refresh a page the recording begins automatically and stops when the page has loaded. Is there a way to 1)Start this recording in the background automatically without needing to open developer tools in chrome/node-webkit window . Maybe the recording can be enabled via some Chrome API which can be called when the application loads 2)Dump the recorded data into a log file (e.x. a json file) once the recording is over. Any pointers in the