From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.help Subject: Re: Why emacs touches read-only file? Date: Thu, 19 Apr 2007 00:51:48 -0700 Organization: None Message-ID: References: <1176920422.786251.122770@d57g2000hsg.googlegroups.com> <1176957833.977449.134340@e65g2000hsc.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1176971770 30510 80.91.229.12 (19 Apr 2007 08:36:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 Apr 2007 08:36:10 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Apr 19 10:36:04 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HeS7W-0000HC-BT for geh-help-gnu-emacs@m.gmane.org; Thu, 19 Apr 2007 10:36:02 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HeSCR-0004F9-Dm for geh-help-gnu-emacs@m.gmane.org; Thu, 19 Apr 2007 04:41:07 -0400 Original-Path: shelby.stanford.edu!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 11 Original-NNTP-Posting-Host: xoc2.stanford.edu Original-X-Trace: news.Stanford.EDU 1176969108 9972 171.64.109.31 (19 Apr 2007 07:51:48 GMT) Original-X-Complaints-To: news@news.stanford.edu X-Spook: remailer Jamaat ul-Fuqra CNDD Al-Fatah lead azide ANO X-Ran: n0xHowkWw2!Fd7{~5+A+pC>hS0jdJ@\4O"q!0A?c&GK@* List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:42814 Archived-At: Daniel wrote: > It is very weird. In my work place, I was using REDHAT 9 and SUSE 9.3. > In there, emacs (21) write the buffer regardless of the file > permission. Even if you start it with the options -q --no-site-file? If it works OK with -q, there is something in your ~/.emacs file (or system default.el file) to blame. If it works OK with --no-site-file, there is some problem in your system's site-start.el file.