Message: previous - next
Month: January 2012

Re: [trinity-devel] Configuring Kate

From: Keith Daniels <keithwdaniels@...>
Date: Wed, 18 Jan 2012 00:06:25 -0500
On Tue, Jan 17, 2012 at 10:43 PM, Darrell Anderson
<humanreadable@...> wrote:
>> > Any ideas how to fix this?
>> Seconded.
>> In general, Can I force kate to ONLY  use one window?
>> we need a way to always to it :-)
> I presume you can duplicate the problem?
> There also is the problem of Kate not correctly grabbing focus (bug report 692).
> To me Kate has been broken since moving away from a multiple document interface (MDI) to a single document interface (SDI). I don't know how much work is needed to revert to the older code or whether there is sufficient interest among users to motivate us to investigate.
> The MDI to SDI change occurred after 3.4.3. That means 3.5.0 introduced the confounded Kate sessions and the SDI.
> I have all of the 3.4.3 code. Reverting back also would mean restoring the simpler and more effective Projects rather than sessions.
> Is anybody interested?
> Darrell
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> Read list messsages on the Web archive:
> Please remember not to top-post:

I am using Firefox 2.5.24 with Trinity 3.5.12 and Kate will not work
at all if I set the editor in the Web Extensions addon using it's

I either got an error message saying it will not start or nothing
happened if I only used the full path: /opt/kde3/bin/kate.

So, I typed about:config in the address bar and when it's window came
up I typed editor in the search bar.

This brought up several options and I changed these options to this

View_source.editor.args        user set     string       -u

View_source.editor.external   user set     boolean    true

View_source.editor.path        user set     string     /opt/kde3/bin/kate

After doing that Firefox and Kate worked exactly like you want.

I personally don't want to have the web page appear in a kate instance
that I am already working in, so after testing I removed the -u

I was like you orginally, in that I did not like sessions either.

Mostly what I did not like was that you had to start out using a
session--even if it was only a blank default session--and it always
asked you what session you wanted on startup.  I didn't want a
session, I didn't want to be asked about one, I wanted a blank kate
window.  Then later, if I wanted to make it a session--I would save it
as such.

After a lot of hammering, screaming and kicking I got it to work the
way I wanted.  Now that sessions work "my way" I use sessions heavily
and like them a lot.  So please don't make them go away...