On 25 July 2017 at 00:05, Ed Greshko <ed.gres...@greshko.com> wrote: > On 07/25/2017 05:01 AM, Emmett Culley wrote: >> Who decided that I should not be able to use a GUI editor on the servers >> that I manage? >> >> For the first time since Fedora first became available I am truly sorry I >> updated to the current release. Even the switch to KDE4 was not such a >> problem. At least a few developers didn't decide for me how to manage my >> systems. >> >> I haven't heard anything about this, why is it such a secret? How can I fix >> this as I am effectively crippled. I use nano for most work on remote >> servers, But fro all of the server that have a GUI installed we use (used) >> kwrite. > > > You could, of course, do what it says to do.... > > [egreshko@meimei ~]$ sudo kwrite > [sudo] password for egreshko: > Executing KWrite as root is not possible. To edit files as root use: > SUDO_EDITOR=kwrite sudoedit <file> > > You also have to be in a directory that isn't owned by you to start the > process. I > guess it is an inconvenience but since I only use vi it doesn't bother me. > > Since kwrite is a KDE application you may want to ask the folks on the KDE > list. > >
One of the problems with the SUDO_EDITOR approach is that it doesn't save the changes to the file until you close the file in kwrite, which is annoying to say the least. Here's the upstream commit: https://cgit.kde.org/kate.git/commit/?id=9adcebd3c2e476c8a32e9b455cc99f46b0e12a7e -- Ahmad Samir _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
