On 02/12/16 11:13, ads wrote:
Thanks for the suggestion.
I looked at strace, but couldn't see any obvious cause (no EPERM for
example). I set up a new user where it all worked properly, so I
started to try and find a difference, and realised that my normal
userid uses gvim (echo $EDITOR -->
Thanks for the suggestion.
I looked at strace, but couldn't see any obvious cause (no EPERM for
example). I set up a new user where it all worked properly, so I started
to try and find a difference, and realised that my normal userid uses gvim
(echo $EDITOR --> gvim) while my new test user uses
On 01/12/2016 12:20, ads wrote:
If I do mkdir /dev/shm/foo, then touch /dev/shm/foo/bar, the file bar
gets written correctly.
And what if you do "gvim /dev/shm/foo/bar" ?
Is it possible that there is an apparmor policy for gvim, which is
preventing it opening files under /dev ?
Somebody
Hi,
On Dec 1, 2016 10:53 AM, "ads" wrote:
>
> I apologise for re-opening this topic. I did not receive the reply kindly
sent me by Renato Alves other than as part of a daily digest (I had only
subscribed to digests) and I don't know how to simulate a reply to keep the
old thread
I apologise for re-opening this topic. I did not receive the reply kindly
sent me by Renato Alves other than as part of a daily digest (I had only
subscribed to digests) and I don't know how to simulate a reply to keep the
old thread going.
My original query was as follows:
When I try to edit an
When I try to edit an existing password using vim, when it comes time to
save (I enter :w as a vim command) I get a message
"/dev/shm/pass.tQVSIzXmX17hI/McsB5-test-pass.txt" E212: Cannot open file
for writing
"/dev/shm/pass.BrDRETCxY0V0s/DlvET-visa...3603.txt" E212: Cannot open file
for