From: ken <gebser@mousecar.com>
To: help-gnu-emacs@gnu.org
Subject: "Text is read-only"... except it isn't... or shouldn't be
Date: Mon, 13 May 2013 05:47:46 -0400 [thread overview]
Message-ID: <5190B6C2.3060801@mousecar.com> (raw)
A file which I've been opening in emacs and editing for a few years in
emacs suddenly with emacs version 22.1.1 became read-only. I open it,
can navigate around in it (though the cursor/mark isn't visible), but
when I try to edit it, I'm not allowed. I get a message in the
minibuffer saying, "Text is read-only". The beginning of the modeline
is "-u: --". I can open this same file in vi and edit it (as the same
user) without any problem at all. I don't have this problem with any
other file I edit in emacs, just this one. The OS is linux, kernel
version 2.6.18.384, and the permissions for this file are 664 and I am
the owner of the file. If I change (i.e., mv) the name of the file to
something else, emacs behaves normally and lets me edit the file just
like any other file. So I'm pretty sure that the problem is that emacs
has a problem with the file name and thinks I shouldn't be allowed to
edit it. How do I turn this behavior off?
thanks much.
next reply other threads:[~2013-05-13 9:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 9:47 ken [this message]
2013-05-13 16:13 ` "Text is read-only"... except it isn't... or shouldn't be Eli Zaretskii
2013-05-13 16:51 ` ken
2013-05-13 17:08 ` Eli Zaretskii
2013-05-14 2:34 ` ken
2013-05-14 6:46 ` Eli Zaretskii
2013-05-14 8:59 ` Peter Dyballa
2013-05-14 12:22 ` ken
2013-05-14 13:39 ` Eli Zaretskii
2013-05-14 20:39 ` ken
2013-05-14 20:42 ` Eli Zaretskii
2013-05-14 20:45 ` Jai Dayal
2013-05-14 21:39 ` Óscar Fuentes
2013-05-14 23:23 ` How to unsubscribe (was: "Text is read-only"... except it isn't... or shouldn't be) Bob Proulx
2013-05-15 2:16 ` Jai Dayal
2013-05-15 7:23 ` Eli Zaretskii
2013-05-16 12:50 ` Suvayu Ali
2013-05-14 21:36 ` "Text is read-only"... except it isn't... or shouldn't be ken
2013-05-15 5:17 ` Kevin Rodgers
2013-05-15 7:28 ` Eli Zaretskii
2013-05-15 11:56 ` ken
2013-05-15 12:30 ` Eli Zaretskii
[not found] ` <mailman.25840.1368618972.855.help-gnu-emacs@gnu.org>
2013-05-16 3:49 ` Jason Rumney
2013-05-15 11:48 ` ken
2013-05-16 6:27 ` Kevin Rodgers
2013-05-16 11:08 ` Essential question [re: Re: "Text is read-only"... except it isn't... or shouldn't be] ken
2013-05-16 13:30 ` Kevin Rodgers
2013-05-16 14:26 ` ken
2013-05-16 14:39 ` Peter Dyballa
2013-05-18 13:59 ` Kevin Rodgers
2013-05-19 12:10 ` ken
2013-05-16 14:23 ` ken
2013-05-16 14:41 ` Peter Dyballa
2013-05-16 14:48 ` Dmitry Gutov
2013-05-16 22:00 ` Xue Fuqiao
2013-05-14 11:58 ` "Text is read-only"... except it isn't... or shouldn't be ken
2013-05-13 17:59 ` ken
2013-05-13 18:10 ` Eli Zaretskii
2013-05-13 18:15 ` Bob Proulx
2013-05-14 2:26 ` ken
[not found] ` <mailman.25692.1368498372.855.help-gnu-emacs@gnu.org>
2013-05-14 2:38 ` Barry Margolin
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=5190B6C2.3060801@mousecar.com \
--to=gebser@mousecar.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).