[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 296590] Kate can  not edit a file for which I have the write access
From:       Tim Holy <holy () pcg ! wustl ! edu>
Date:       2012-05-28 15:11:13
Message-ID: bug-296590-17878-7JFTjTjnPw () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=296590

Tim Holy <holy@pcg.wustl.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |holy@pcg.wustl.edu

--- Comment #7 from Tim Holy <holy@pcg.wustl.edu> ---
I saw the forum post before noticing this bug report. Here's a copy of the
reply I posted there:

The same issue bit me. I tried copying the file to a new name, and kate could
edit it fine, so I knew it wasn't a problem with the file.

So I poked around in .kde and found this file:
~/.kde/share/apps/kate/metainfos. It seems to contain a listing of metadata for
each file in kate's (recent?) history. I found the troublesome file, and saw
that the "ReadWrite" tag had been set to "false". I changed it (using a
different text editor for safety!), and presto, I can edit my file again.

I have no idea what triggered the ReadWrite setting to change, but now that I
know about this, I'll be alert for it. If anyone else discovers the pattern and
can reproduce it, clearly that would be helpful to the developers.

Extra note: the original file had been created by kate, I was able to edit it
for several months using kate, and suddenly one day kate stopped being able to
make changes. That was long enough ago that I can't remember what conditions
might have triggered the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]