From: Daniel <hanmoai@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Why emacs touches read-only file?
Date: 20 Apr 2007 00:00:57 -0700 [thread overview]
Message-ID: <1177052457.225050.244290@b58g2000hsg.googlegroups.com> (raw)
In-Reply-To: <87zm53ye2l.fsf@lion.rapttech.com.au>
On Apr 19, 7:28 pm, Tim X <t...@nospam.dev.null> wrote:
> Daniel <hanm...@gmail.com> writes:
> > Hi all,
>
> > 1. Create a file with permission of 444 (read-only) file.
> > 2. Open the file using emacs.
>
> > Question.
>
> > My emacs open the read-only file as writable buffer. Also, I can
> > modify it and save it. (AMAZING, emacs IGNORES unix file system. WOW.)
>
> > What happened to the emacs, and how it works properly (open files as
> > read-only if it is read-only, and as writable if it is writable.)
>
> > Thank you,
>
> > Dan.
>
> doing the same thing with emacs 22 gives me a read only file. any attempt to
> modify the file gives me a buffer is read only message.
>
> Your not running as root are you?
>
> Tim
>
> --
> tcross (at) rapttech dot com dot au
I am running it as root, but the permission is read-only to root also.
Is there any problem?
next prev parent reply other threads:[~2007-04-20 7:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 18:20 Why emacs touches read-only file? Daniel
2007-04-18 18:49 ` Eric Hanchrow
2007-04-18 19:22 ` Glenn Morris
2007-04-19 3:00 ` Matthew Flaschen
2007-04-19 4:43 ` Daniel
2007-04-19 7:51 ` Glenn Morris
2007-04-19 18:09 ` Daniel
2007-04-19 19:07 ` Peter Dyballa
[not found] ` <mailman.2277.1177009971.7795.help-gnu-emacs@gnu.org>
2007-04-19 21:28 ` Daniel
2007-04-20 1:02 ` EMacs & X-windows "Wilfred Zegwaard (privé)"
2007-04-20 9:03 ` Peter Dyballa
2007-04-19 10:07 ` Why emacs touches read-only file? Arne Schmitz
2007-04-19 18:10 ` Daniel
2007-04-20 2:28 ` Tim X
2007-04-20 7:00 ` Daniel [this message]
2007-04-20 14:51 ` Daniel
2007-04-21 3:48 ` Tim X
2007-04-21 12:46 ` Johan Bockgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1177052457.225050.244290@b58g2000hsg.googlegroups.com \
--to=hanmoai@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).