Kate running really choppy - keeps writing to disk for each character!
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
However with my new distro (Kubuntu) this option no longer fixes the issue. I can see a huge increase in NFS traffic when I hold down a key with tcpdump running. Local files edit fine, but remote ones are very slow.
Is there a way to stop it from always writing to the file and only write to the file when I actually save? Moving files back and forth is not an option I need to be able to edit directly on the NFS share. Oddly, I have a gigabit link to the server and we're talking KB worth of traffic not even MB so I don't know why it's even slow to begin with.
I'm also open to an alternative editor if there's no way to stop this behavior, but I do like Kate compared to all the other ones I tried.
I also see a .kate-swp file that gets created as soon as I touch a key, so it almost seems like it's not honoring that setting.
Last edited by Red Squirrel; 09-22-2013 at 12:08 AM.
open kate
click settings / configure kate
click on the "open / save" option in the left window
click the Advanced tab
put a check in " Disable file swap syncing "
Distribution: Mint 20.1 on workstation, Debian 11 on servers
Posts: 1,327
Original Poster
Rep:
Yep tried that, that USED to fix the issue, but for some reason in this version (3.10.5) it's not. If I show hidden file I can see the swap file be created as soon as I hit any key.
Distribution: Mint 20.1 on workstation, Debian 11 on servers
Posts: 1,327
Original Poster
Rep:
Bump in case anyone happens to know a fix for this. Still an issue. Since I moved to my new file server I don't see the issue as much since it has faster controllers, but if it's bogged down I see the issue. The real problem here is that it should NOT be trying to write to the file server while editing, there is no reason for this, it should only read or write if I click save. It creates a "swap" file despite that option being off. Is there a way I can at least move the location of those swap files locally?
Is there another editor that is as intuitive to use as Kate? This issue is very irritating. I can barely code anything if there's any kind of job going on that's accessing the file server. This is a retarded "feature" especially considering they changed it so the check box to disable it does not disable it anymore. I'm not going to start coping all my files locally back and forth that's a pain in the ass. I use NFS so I can centralize everything and make backups easier.
Last edited by Red Squirrel; 03-08-2014 at 01:30 AM.
Distribution: Mint 20.1 on workstation, Debian 11 on servers
Posts: 1,327
Original Poster
Rep:
Bump, anyone?
I suppose I can just download the source and fix this myself but a proper solution would be better so I don't have to try to mess with making a custom version integrate with the system. I'll lose any GUI related stuff like having it show up in a list so I can set a file type to open with it by default, and other stuff like that.
Distribution: Mint 20.1 on workstation, Debian 11 on servers
Posts: 1,327
Original Poster
Rep:
Ended up just switching to Gedit. It's too bad though that such a silly little thing has crippled Kate. Making that checkbox for disabling file syncing actually do what it says it does would fix the issue.
Distribution: Mint 20.1 on workstation, Debian 11 on servers
Posts: 1,327
Original Poster
Rep:
This is STILL an issue. Why is this not fixed? I can't be the only one that uses NFS to store data and code directly off the share. I tend to work on code related projects on and and off and often find myself giving up because of this, it's completely ridiculous. I have 3 backup jobs running right now on my file server and I can't even code because the disk I/O is crippled (that's another issue I've been fighting with... it should not cripple the I/O that badly). The ability to type in a text editor should not be dependent on disk I/O. That's what ram is for. It should at least store chunks of the open document in ram, but really, for documents in the KB there's no reason why it can't just store it in ram and keep it in ram and work on it in ram.
Is there a way to fix this issue? Like I said before, the option to disable file syncing does not work. I have proven this out with a packet sniffer. Holding down a key generates TONS (100's of pages) of NFS packets.
I cannot find an alternative text editor that is as usable as Kate, the others all have quirks or lack certain features. How do I get into contact with someone to actually get the ball rolling to fix this issue?
Update : This is fixed in version 16
And are two new settings: how often to sync, so if you do want a backup but you don't want every keystroke clogging your network, you can just update every x seconds; and sync to a different folder, so if you're working on a remote file you can keep your backup local.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.