From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: D. Power <powerd@pcisys.net.invalid>
Cc: help-gnu-emacs@gnu.org
Subject: Re: A problem with read-only in emacs
Date: Sun, 27 Jul 2008 20:52:04 +0200 [thread overview]
Message-ID: <1781D80D-AF48-4A5A-941D-6F99E0FA2344@Web.DE> (raw)
In-Reply-To: <powerd-DDA8E6.21454126072008@news.pcisys.net>
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.
next prev parent reply other threads:[~2008-07-27 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 3:45 A problem with read-only in emacs D. Power
2008-07-27 4:33 ` Tim X
2008-07-27 17:08 ` D. Power
2008-07-27 18:52 ` Peter Dyballa [this message]
[not found] ` <mailman.15478.1217191848.18990.help-gnu-emacs@gnu.org>
2008-07-27 22:21 ` D. Power
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=1781D80D-AF48-4A5A-941D-6F99E0FA2344@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=powerd@pcisys.net.invalid \
/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).