On 07/25/2017 07:30 PM, Emmett Culley wrote: > On 07/24/2017 06:41 PM, Ed Greshko wrote: >> On 07/25/2017 08:52 AM, Emmett Culley wrote: >>> On 07/24/2017 03:05 PM, Ed Greshko 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. >>>> >>>> >>> Unfortunately, doing what it says to do doesn't work. >>> >> >> Works just fine for me. >> >> Maybe you need to define "doesn't work". >> >> But, what Rex has said it true and easier. And, the reason the developers made the >> changes have nothing to do with "you". :-) >> >> > I did finally get sudoedit to work. Yesterday I set SUDO_EDITOR=kwrite in a bash shell environment, but sudoedit kept loading nano. But today sudoedit loads kwrite. Unfortunately that is unworkable as well, as it hangs up on the save dialog when attempting to exit without saving. Saving explicitly before attempting to exit does work, however. AFAIK sudoedit was never intended to be used with a GUI-based editor, which is why it defaults to using nano or vim. If you have it invoke a GUI editor, you're going to have issues with pop-up dialogs as it has no concept of what those are. > So I now have a workaround. Two workarounds. > > And of course these changes have nothing to do with me personally. However making these kinds of changes to save a noob from shooting off his/her foot is still not a good reason to cause experienced users all this pain. There must be a better way. Take it up with the so-called steering committees. There are a bunch of (IMHO) idiotic decisions made to Linux in the last few years--either just really bad choices (journald, etc.) or the selection of mechanisms that are nowhere near baked enough for general use (systemd for example). Obviously just my opinions, but based on >40 years of working in the IT field. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Blessed be the peacekeepers, for they shall be shot at from - - both sides. - - -- A.M. Greeley - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
