what the hell is wrong with kwrite, kedit, kword, k evertying?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
what the hell is wrong with kwrite, kedit, kword, k evertying?
i need to edit a file, and i need to be under root
under root, i type kedit
says command not found
i type kwrite
says command not found
thign is i installed all the packages, and i can use kwrite to open the file if i right click the file in graphical mode and select "open with kwrite" but the problem is that if i do that, i am not under root and therefore i cannot write in the file
but under root, when i type in kwrite it says command not found!
As a normal user type 'whereis kedit' and look at the paths it gives you. Find the path that the kedit executible is in and add it to your root ~/.bashrc
Originally posted by Luantum As a normal user type 'whereis kedit' and look at the paths it gives you. Find the path that the kedit executible is in and add it to your root ~/.bashrc
Location: The land of the free and the home of the brave
Distribution: Slack 10
Posts: 239
Rep:
1. cp ~/.bashrc ~/.bashbackup
2. *name of text editor* ~/.bashrc
3. go to an empty line
4. write on empty line:
[code]export PATH=$PATH:/pathoffile
5. save
6. exit editor
7. send me some money
8. type the same thing into your regular console
9. w00t
10. send me more money
11. Congradulations, you are now a h4x0r
Originally posted by Squall 1. cp ~/.bashrc ~/.bashbackup
2. *name of text editor* ~/.bashrc
3. go to an empty line
4. write on empty line:
[code]export PATH=$PATH:/pathoffile
5. save
6. exit editor
7. send me some money
8. type the same thing into your regular console
9. w00t
10. send me more money
11. Congradulations, you are now a h4x0r
I can think of a couple of things wrong with this...
2. the person is trying to fix a trouble with his text editor not being in his path, so "*name of text editor* ~/.bashrc" isn't going to do squat.
4. this needs fixin..."[code]" has nothing to do with bash variables
11. a "h4x0r" probably wouldn't be using Kwrite
7. & 10. $$ > Squall (there's you money =oD)
As an alternative, Vim is an excellent editor for both user and root...type "vimtutor" for some help
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.