Comments for Kate | Get an Edge in Editing

Comment on Maintainer Needed: Kate – External Tools Plugin by Kaitain

Kaitain — Thu, 17 May 2012 03:14:41 +0000

Sigh. This is the last straw for me. I’ve been trying to learn assembler on Linux using Jeff Duntemann’s book, and there were various things mentioned in it that had changed radically in the last two years (since it was written). I’ve just about managed to get workarounds for most of them, but Kate is the main tool used and there’s no workaround for this plugin’s disappearance.

The Linux environment is clearly too inconsistent and unreliable to make learning from a textbook viable. The ground just keeps shifting under your feet. I’m going back to Macs.

Comment on Code Folding Updates by Dominik

Dominik — Wed, 16 May 2012 17:53:05 +0000

No, currently not.

Comment on Code Folding Updates by Jon Stephan

Jon Stephan — Wed, 16 May 2012 12:59:55 +0000

I know this is an old thread, but this change just recently percolated to my machine. I liked the old rainbow colors… is there any way to get them back? Please?

Thanks,
-Jon

Comment on Scripting in Kate by Dominik

Dominik — Wed, 16 May 2012 07:24:01 +0000

For a lot of stuff you can use the text filter plugin and pipe selected text through external programs, and with that you can e.g. reformat the text.

But right, a js function to invoke external programs does not exist, yet. How would it look like? system.exec(“app with parameters”) ?

Comment on Scripting in Kate by Dominik

Dominik — Wed, 16 May 2012 07:21:59 +0000

Auto brackets will ignore the ‘)’ if it already exists, i.e. Kate in KDE 4.9 will have this behavior.

Comment on RFC: Exporting JavaScript API by ahiemstra

ahiemstra — Sun, 13 May 2012 13:23:36 +0000

There are two things you can do, the way I see it:

1. Use dynamic binding to add methods and properties to the document. Not sure how feasible this is especially when dealing with C++ methods, but basically, instead of having a KileScriptDocument class and setting document to that, you’d use setProperty() on the KateScriptDocument to add properties, including function objects. Basically this is how you would do it in pure JavaScript.

2. Use the facade pattern. You create a class KileScriptDocument with a member KateScriptDocument. Then you need to implement every method that you want to expose of KateScriptDocument in KileScriptDocument. Leads to quite some duplication, but has the advantage that you can hide methods that would not be relevant for your situation.

Comment on Maintainer Needed: Kate – External Tools Plugin by Evan

Evan — Sun, 13 May 2012 02:23:32 +0000

I have tried to get this back by reverting the commits

daea2a02e00007955cbcc892f0f5b06b0d8e6d9a
60ceb16f288b276a0b8b835e589244c4551d4403
798ae2fd2a2334515fe6d3592bbc3e71473840bb

However, after I rebuild kate, the plugin still does not appear in the plugin list.

Comment on Some Kate Color Schemas by Flo R Moser

Flo R Moser — Tue, 08 May 2012 19:36:44 +0000

any chance of getting the oblivion-coast theme for kate 4.8?

Comment on Scripting in Kate by cgk

cgk — Fri, 04 May 2012 02:23:41 +0000

So is there any chance it will be possible to invoke external programs in future versions of Kate scripting? I’ve looked into this multiple times, but always found that the APIs provided are simply not sufficient to do what I want. This would not be such a problem if it was possible to invoke external programs to do the actual work (e.g., python scripts).

Additionally, I have some external programs which do non-trivial stuff (e.g., code reformatting). I seriously do not want to replicate them in javascript, especially not since I already *have* working programs and all I would need would be a way to get the text into them, and out of them using the scripts.

Comment on Maintainer Needed: Kate – External Tools Plugin by Danilo

Danilo — Thu, 03 May 2012 14:10:27 +0000

Please, take this tool back. I usally use it every day too. I’m being pratically forced to change my favorite editor.