From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: notbob Newsgroups: gmane.emacs.help Subject: Re: why read only buffer? Date: 6 Jul 2012 21:50:53 GMT Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1341611715 8113 80.91.229.3 (6 Jul 2012 21:55:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 6 Jul 2012 21:55:15 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jul 06 23:55:15 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SnGUc-0002Nm-5v for geh-help-gnu-emacs@m.gmane.org; Fri, 06 Jul 2012 23:55:14 +0200 Original-Received: from localhost ([::1]:36571 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SnGUb-00083a-8S for geh-help-gnu-emacs@m.gmane.org; Fri, 06 Jul 2012 17:55:13 -0400 Original-Path: usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 30 Original-X-Trace: individual.net E4okU9HqA/dv3PjM9dJdhAGFh4wOaUUqZQkda6XTaeD4hiyt3EfdUk0ObLpvcwj88D Cancel-Lock: sha1:hI16LKZlf67tIOwquPMYIcdSJiM= User-Agent: slrn/0.9.9p1 (Linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:193319 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:85706 Archived-At: On 2012-07-06, PJ Weisberg wrote: > That's deliberately there to stop you from accidentally modifying a > backup file when you meant to be working with the regular file. If > you searched through the source you'd find this in files.el: Yeah, that's not gonna happen. ;) What I seem to recall is, backup files were progressively renamed for more than on "back-up", as in foo~1, foo~2, or something similar. Perhaps I'm thinking of jed. I'm old. I ferget. ;) > > ----- > ;; Make people do a little extra work (C-x C-q) > ;; before altering a backup file. > (when (backup-file-name-p buffer-file-name) > (setq buffer-read-only t)) > ----- So, how does none set it to make it overwriteable, by default. Jes delete the above code? nb -- vi --the heart of evil!