SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slint64-14.2rc on Lenovo Thinkpad W520
Problems using kate
I recently began using kate (under fluxbox in Slackware 14.0).
I did that because its syntax highlighter is way better than geany's for shell scripts and have some handy features, though it be slow to start and spit a lot of garbage on my xterm (thanks /dev/null to take care of that :-)
But I founded some problems using it:
(1) It has problems to deal with situations when the same file is opened more than once
(2) It happens to pretend that it has saved a file, but actually didn't. That is *very* annoying. That made me spend *hours* to (not) find bugs... that actually didn't exist.
Is it that kate hates me or (I would prefer that) a PEBKAC case? May be I don't use it properly?
Last edited by Didier Spaier; 03-27-2013 at 07:39 PM.
I've have opened files in Kate that were open in Kompozer and had the two applications work together just fine. Changes saved in Kate displayed in Kompozer and vice versa.
I just tried to load the same file in two instances of kate. It didn't like it. I opened two instances of Kate and loaded the same file. I then made and saved changes in Instance One; when Kate Instance two prompted me that the file had been changed and I clicked to reload, Instance Two closed and Instance One took focus.
I've also never had a problem saving a file, at least not one that failed to throw an error message, usually permissions.
For testing, I'd suggest starting kate from the command line and trying some things. Maybe it will show some error messages in the terminal that could shed some light on this.