Same problem here. I figred out two ways to work around this problem:
1) delete .nano_history (since the file doesn't exist, nano is able to create it using the user's rights. I don't know about any bad consequences this might have?) 2) change .nano_history's permissions (for some strange reason I am unable to reproduce this behavior while writing this...) It should be possible to do both using a cron job - but there should be a better way? -- Need better way of handling permissions with nano and sudo mix https://launchpad.net/bugs/72995 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
