Why emacs touches read-only file?

Why emacs touches read-only file?

[Daniel]

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.

Re: Why emacs touches read-only file?

[Eric Hanchrow]

    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. 

Mine doesn't.
                                                         
    Also, I can modify it and save it. (AMAZING, emacs IGNORES unix
    file system. WOW.)

Sounds like a bug.  Please report it by doing M-x report-emacs-bug
RET.  Also be sure to read (info "(emacs)Bugs").

-- 

Re: Why emacs touches read-only file?

[Glenn Morris]

Daniel wrote:

> 1. Create a file with permission of 444 (read-only) file.

OK:

touch 1
chmod 444 1

> 2. Open the file using emacs.

OK:

emacs-21.3 -q --no-site-file 1

> My emacs open the read-only file as writable buffer.

Mine doesn't: "Note: file is write protected"

> Also, I can modify it and save it.

I can't: "Buffer is read-only: #<buffer 1>".


I can if I do M-x toggle-read-only, but then when I go to save the
file I am prompted "File 1 is write-protected; try to save anyway?".
This all seems pretty robust.


> (AMAZING, emacs IGNORES unix file system. WOW.)

Not really. It does what you tell it do, and provides you with plenty
of notification as it does so.


> 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.)

As described, your Emacs is not behaving in the standard way, so
something on your system must be making it act like this.

Re: Why emacs touches read-only file?

[Matthew Flaschen]

Glenn Morris wrote:
> Daniel wrote:
> 
>> 1. Create a file with permission of 444 (read-only) file.
> 
> OK:
> 
> touch 1
> chmod 444 1
> 
>> 2. Open the file using emacs.
> 
> OK:
> 
> emacs-21.3 -q --no-site-file 1
> 
>> My emacs open the read-only file as writable buffer.
> 
> Mine doesn't: "Note: file is write protected"
> 
>> Also, I can modify it and save it.
> 
> I can't: "Buffer is read-only: #<buffer 1>".
> 
> 
> I can if I do M-x toggle-read-only, but then when I go to save the
> file I am prompted "File 1 is write-protected; try to save anyway?".
> This all seems pretty robust.

However, if you then choose yes, it will allow you to save if you have
permissions to give yourself write access.  Moreover, the file will go
back to being read-only afterwards, which is a bit strange.

Matthew Flaschen

Re: Why emacs touches read-only file?

[Daniel]

On Apr 18, 12:22 pm, Glenn Morris <rgm+n...@stanford.edu> wrote:
> Daniel wrote:
> > 1. Create a file with permission of 444 (read-only) file.
>
> OK:
>
> touch 1
> chmod 444 1
>
> > 2. Open the file using emacs.
>
> OK:
>
> emacs-21.3 -q --no-site-file 1
>
> > My emacs open the read-only file as writable buffer.
>
> Mine doesn't: "Note: file is write protected"
>
> > Also, I can modify it and save it.
>
> I can't: "Buffer is read-only: #<buffer 1>".
>
> I can if I do M-x toggle-read-only, but then when I go to save the
> file I am prompted "File 1 is write-protected; try to save anyway?".
> This all seems pretty robust.
>
> > (AMAZING, emacs IGNORES unix file system. WOW.)
>
> Not really. It does what you tell it do, and provides you with plenty
> of notification as it does so.
>
> > 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.)
>
> As described, your Emacs is not behaving in the standard way, so
> something on your system must be making it act like this.

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. I am using Ubuntu in my home, and installed "GNU Emacs
22.0.50.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
2006-09-19 on rothera, modified by Debian", which works properly.

Hmm...Something wrong in the emacs in SUSE 9.3 or REDHAT 9. How can I
fix the problem? What part should I see?

Re: Why emacs touches read-only file?

[Glenn Morris]

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.

Re: Why emacs touches read-only file?

[Arne Schmitz]

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. I am using Ubuntu in my home, and installed "GNU Emacs
> 22.0.50.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
> 2006-09-19 on rothera, modified by Debian", which works properly.
> 
> Hmm...Something wrong in the emacs in SUSE 9.3 or REDHAT 9. How can I
> fix the problem? What part should I see?

Does the file you have edited by any chance reside on a networked mount? 

Arne

-- 
[--- PGP key FD05BED7 --- http://www.root42.de/ ---]

Re: Why emacs touches read-only file?

[Daniel]

On Apr 19, 12:51 am, Glenn Morris <rgm+n...@stanford.edu> wrote:
> 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.

No. I tried to run "emacs -q 1" and "emacs --no-site-file 1" and
"emacs -q --no-site-file 1", but all of them are not working properly
with read-only file.

BTW, I am seeing the REDHAT or SUSE linux via VNC Client. Is this
causing the problem?

Re: Why emacs touches read-only file?

[Daniel]

On Apr 19, 3:07 am, Arne Schmitz <arne.schm...@gmx.net> wrote:
> 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. I am using Ubuntu in my home, and installed "GNU Emacs
> > 22.0.50.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
> > 2006-09-19 on rothera, modified by Debian", which works properly.
>
> > Hmm...Something wrong in the emacs in SUSE 9.3 or REDHAT 9. How can I
> > fix the problem? What part should I see?
>
> Does the file you have edited by any chance reside on a networked mount?
>
> Arne
>
> --
> [--- PGP key FD05BED7 ---http://www.root42.de/---]

Actually, it is not mounted via network. But I am using Linux via VNC
Client. Is this causing the problem? (I don't think so.)

Re: Why emacs touches read-only file?

[Peter Dyballa]

Am 19.04.2007 um 20:09 schrieb Daniel:

> No. I tried to run "emacs -q 1" and "emacs --no-site-file 1" and
> "emacs -q --no-site-file 1", but all of them are not working properly
> with read-only file.

Why are you using the number 1 as an argument?

--
Greetings

   Pete

Some day we may discover how to make magnets that can point in any  
direction.

Re: Why emacs touches read-only file?

[Daniel]

On Apr 19, 12:07 pm, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> Am 19.04.2007 um 20:09 schrieb Daniel:
>
> > No. I tried to run "emacs -q 1" and "emacs --no-site-file 1" and
> > "emacs -q --no-site-file 1", but all of them are not working properly
> > with read-only file.
>
> Why are you using the number 1 as an argument?
>
> --
> Greetings
>
>    Pete
>
> Some day we may discover how to make magnets that can point in any
> direction.

Pete,

It is not the argument. It is the file name as simplified as I can.

EMacs & X-windows

["Wilfred Zegwaard (privé)"]

I'm using EMacs and Windows XP. Is there a way of setting EMacs in a 
X-Windows like environment? I've got a framed environment and I want a 
window-environment. Or do I need KDE for that?

Thanks,

Wilfred

Re: Why emacs touches read-only file?

[Tim X]

Daniel <hanmoai@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

Re: Why emacs touches read-only file?

[Daniel]

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?

Re: EMacs & X-windows

[Peter Dyballa]

Am 20.04.2007 um 03:02 schrieb Wilfred Zegwaard (privé):

> I've got a framed environment

What do you mean with that? A window without decoration?

And, please, could you start a new thread instead of hi-jacking an  
existing one?

--
Greetings

   Pete                                           0
                                            %-/\_//
                                             (*)(*)

Re: Why emacs touches read-only file?

[Daniel]

On Apr 20, 12:00 am, Daniel <hanm...@gmail.com> wrote:
> 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?

I am running it as root, but the permission is read-only to root also.

Is there any problem?

Re: Why emacs touches read-only file?

[Tim X]

Daniel <hanmoai@gmail.com> writes:

> 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?
>

Well, there shouldn't be. Some programs will allow root to edit read only files
and will only give a warning. However, I just tried it with emacs 22 and it
won't let me edit it unless I specifically ask it to. So, its probably not an
issue. Still, running as root is generally considered a bad thing as it is way
too easy to accidently change things. It can also undermine the protection
Unix/GNU Linux users generally have against viruses, trojans etc. Many people
are under the mistaken belief that you cannot get such things under Unix/GNU
Linux. However, this is not true. If your running as root it is possible for
your system to be compromised by most of the same techniques used on Windows,
such as malicious e-mail attachments or web sites that attempt to take
advantage of security weaknesses in browsers/browser plugins etc. . Of course,
because most people don't run as root and as there are considerably more
variables involved, there are few examples of attacks setup like this - most
Unix/Gnu Linux attacks concentrate on more network type weaknesses. Still,
running as root pretty much compromises the security model that the system is
based on.

There has been a number of users who have posted that they cannot reproduce the
behavior you are seeing. This would indicate it is something specific to your
setup. Possibly in your .emacs or emacs site file, possibly related to the fact
your accessing via VNC and the way it is configured. Have you tried doing the
same with other programs, such as vi? Have you tried doing the same in
different directories/partitions? Have you tried doing the same, but when not
running as root? 

Tim

-- 
tcross (at) rapttech dot com dot au

Re: Why emacs touches read-only file?

[Johan Bockgård]

Daniel <hanmoai@gmail.com> writes:

> I am running it as root,

That's why.

> but the permission is read-only to root also.

The behavior was changed in Emacs 22. From etc/NEWS:

    *** When you are root, and you visit a file whose modes specify
    read-only, the Emacs buffer is now read-only too. Type C-x C-q if
    you want to make the buffer writable. (As root, you can in fact
    alter the file.)

And the corresponding antinews[1] entry:

   * When you are logged in as root, all files now give you writable
     buffers, reflecting the fact that you can write any files.


[1] "For those users who live backwards in time, here is information
  about downgrading to Emacs version 21.4."
  (info "(emacs)Antinews")

-- 
Johan Bockgård