A problem with read-only in emacs

A problem with read-only in emacs

[D. Power]

Hi,

I hope someone can help me with this little problem.  It seems that I 
(or the keyboard-walking kitten) have somehow changed the settings in 
emacs (21.2.1) so that new files are created as read-only, so I have to 
chmod any new file before I can edit it.  What have I (or the kitten) 
done, and how can I undo it?

-- 
D. Power
"I hold it to be the inalienable right of anybody to go to hell in his 
own way."
-Robert Frost

Re: A problem with read-only in emacs

[Tim X]

"D. Power" <powerd@pcisys.net.invalid> writes:

> Hi,
>
> I hope someone can help me with this little problem.  It seems that I 
> (or the keyboard-walking kitten) have somehow changed the settings in 
> emacs (21.2.1) so that new files are created as read-only, so I have to 
> chmod any new file before I can edit it.  What have I (or the kitten) 
> done, and how can I undo it?

Maybe set-defa8ult-file-modes will help.

,----[ C-h f set-default-file-modes RET ]
| set-default-file-modes is a built-in function in `C source code'.
| 
| (set-default-file-modes mode)
| 
| Set the file permission bits for newly created files.
| The argument mode should be an integer; only the low 9 bits are used.
| This setting is inherited by subprocesses.
| 
| [back]
`----

regards, 

Tim

-- 
tcross (at) rapttech dot com dot au

Re: A problem with read-only in emacs

[D. Power]

In article <87bq0kuesf.fsf@lion.rapttech.com.au>,
 Tim X <timx@nospam.dev.null> wrote:

> "D. Power" <powerd@pcisys.net.invalid> writes:
> 
> > Hi,
> >
> > I hope someone can help me with this little problem.  It seems that I 
> > (or the keyboard-walking kitten) have somehow changed the settings in 
> > emacs (21.2.1) so that new files are created as read-only, so I have to 
> > chmod any new file before I can edit it.  What have I (or the kitten) 
> > done, and how can I undo it?
> 
> Maybe set-defa8ult-file-modes will help.
> 
> ,----[ C-h f set-default-file-modes RET ]
> | set-default-file-modes is a built-in function in `C source code'.
> | 
> | (set-default-file-modes mode)
> | 
> | Set the file permission bits for newly created files.
> | The argument mode should be an integer; only the low 9 bits are used.
> | This setting is inherited by subprocesses.
> | 
> | [back]
> `----
> 
> regards, 
> 
> Tim


Thanks, I'll look into that.

-- 
D. Power
"I hold it to be the inalienable right of anybody to go to hell in his 
own way."
-Robert Frost

Re: A problem with read-only in emacs

[Peter Dyballa]

Am 27.07.2008 um 05:45 schrieb D. Power:

> It seems that I
> (or the keyboard-walking kitten) have somehow changed the settings in
> emacs (21.2.1) so that new files are created as read-only, so I  
> have to
> chmod any new file before I can edit it.

I don't think that GNU Emacs has this ability – which other tool that  
also can edit files would create read-only files (it won't be able to  
edit and save these edits)? It's likely your run-time environment  
that was changed to create read-only files (and directories). In UNIX  
umask is related to this. When invoked in a shell it well tell you  
its setting, when used with an argument, it will change the recent  
value to the given one. 'umask 022' is a good choice, that can also  
be put into the shell's RC file. For GNU Emacs you should choose 002  
because some (defective?) code high-lights in dired-mode permissions  
of group-writable files by default.

--
Greetings

   Pete

Real Time, adj.:
	Here and now, as opposed to fake time, which only occurs there and  
then.

Re: A problem with read-only in emacs

[D. Power]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

In article <mailman.15478.1217191848.18990.help-gnu-emacs@gnu.org>,
 Peter Dyballa <Peter_Dyballa@Web.DE> wrote:

> Am 27.07.2008 um 05:45 schrieb D. Power:
> 
> > It seems that I
> > (or the keyboard-walking kitten) have somehow changed the settings in
> > emacs (21.2.1) so that new files are created as read-only, so I  
> > have to
> > chmod any new file before I can edit it.
> 
> I don't think that GNU Emacs has this ability ­ which other tool that  
> also can edit files would create read-only files (it won't be able to  
> edit and save these edits)? It's likely your run-time environment  
> that was changed to create read-only files (and directories). In UNIX  
> umask is related to this. When invoked in a shell it well tell you  
> its setting, when used with an argument, it will change the recent  
> value to the given one. 'umask 022' is a good choice, that can also  
> be put into the shell's RC file. For GNU Emacs you should choose 002  
> because some (defective?) code high-lights in dired-mode permissions  
> of group-writable files by default.
> 
> --
> Greetings
> 
>    Pete
> 
> Real Time, adj.:
> 	Here and now, as opposed to fake time, which only occurs there and  
> then.


I wasn't aware of that, thanks.

-- 
D. Power
"I hold it to be the inalienable right of anybody to go to hell in his 
own way."
-Robert Frost