I’m sure I’m just missing something, but I’ve been looking at this for a day or so, and I’m not sure what it is…
I’ve been setting up my UEFI loader, which resides in a protected region on my drive (/boot/efi, owned by root:root with 755 permissions). Inevitably I’ve started up vim in a terminal a few times without root access and been notified that I don’t have write access, at which point I restart it with sudo.
However, sublime has absolutely no problem modifying any of those files when launched as my user. It just doesn’t care. Testcase:
- Launch vim from a virtual console
- Edit my boot configuration file
- Try to save, get error
E212: Can't open file for writing
- Launch sublime from same console
- Successfully make changes
- View file permissions after edit – still no permissions
- Re-launch vim
- See sublime changes, but still can’t edit in vim
Additionally, I’ve opened KSysGuard (KDE’s process monitor) and verified that sublime was indeed launched as my user.
What am I missing?