On 17 January 2012 21:04, Darrell Anderson <humanreadable(a)yahoo.com> wrote: Seconded. In general, Can I force kate to ONLY use one window? we need a way to always to it :-)

On Tue, Jan 17, 2012 at 10:43 PM, Darrell Anderson <humanreadable(a)yahoo.com> wrote: 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 options. 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 configuration: 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... Keith

On Wed, Jan 18, 2012 at 9:07 AM, Patrick Serru <patrick(a)serru.net> wrote: I agree 100%.... I think this attitude by the developers is why so many people are upset with Ubuntu, KDE, Gnome and other software. Please consider what Patrick is saying. Keith

Le mercredi 18 janvier 2012, Keith Daniels a écrit : --------------------------------------------------------------------- (((-: Dont worry, Keith, Tim, the Trinity project leader / manager is attentive to that. I suppose that most of the readers of these 2 lists suffered (yes!) of the direction choosen by KDE developers. For Darrell, if this could help: kwrite is the éditor I use when I simply just want a texte in an editor, even if I prefere kate. There is someone in the users's list that could use kwrite (with firefox), too... Patrick

On 18 January 2012 12:41, Darrell Anderson <humanreadable(a)yahoo.com> wrote: Would the problem be solved with a configuration option to always use the current session?

On Wed, Jan 18, 2012 at 1:18 PM, Darrell Anderson &lt;humanreadable(a)yahoo.com&gt; wrote: Darrell OK, since you promised.... <grin> This is my "Opinion" about how Kate works in relation to being called and/or run with options. It comes from the period when I was kicking and screaming at Kate a lot (and that was several years ago) so there could be a lot of incorrect info here. I tried several ways to get Kate sessions the way I wanted them. After a while I became convinced that most of the settings inter-reacted, conflicted, canceled out, depended on, etc. each other in some manner. You change one setting and it might or might not work depending on the rest of the settings--and "sometimes" other settings started working or stopped working. So being harder headed than a rock I just kept on changing things until one day it worked, and it has worked ever since. During that time, I tried calling kate from the command line with various options, using scripts with various command lines, from specially configured icons as well as changing .desktop files to see if any of those would work. What I noticed first, was that each different method often required different paths and quoting of the arguments and if you didn't get it right--they didn't work at all. Since we are using the same Firefox and I think you are using Trinity 3.5.12 as well--and mine works and yours does not, probably the problem is conflicting settings somewhere in your system. I am also using Ubuntu 10.10 but that is probably not part the problem I think.... Firefox calls Kate directly and does not use a .desktop file, but if I am wrong, some setting either in Firefox's or Kate's desktop files could have a setting in them that over rides the one you put in to Firefox. Or, whatever method you used to block sessions (I'm assuming you did this) could be conflicting with the Firefox call. You might try calling Kate from the command line using: /opt/kde3/bin/kate -u <a valid file name> If this opens in an already open instance of Kate then I would have to assume that Firefox was not calling Kate directly but through a desktop file and start checking them. If it doesn't work then that should give you some clues about what is not working for you. My opinion would be conflicting settings in Kate if the CLI call did not run. Also, this probably has nothing to do with your problem, but it just happened to me and caused some strange problems with Kate and other programs. I had added some user paths to my environment path string and wasn't paying any attention and put my local paths after the system paths. When I reversed that and had my local paths first and system paths last all my problems went away--which I don't really understand. I know that doing that will cause any system file, with the same name as a user executable, to be executed instead of the user's file but why would that affect Kate? I don't see sessions--ever--unless I specifically open or save them, and I have no problem getting --use to work. The way my sessions are setup could be why my Firefox works and yours doesn't. I don't remember what settings I used (and probably never knew) to make my system work like this, but if you wanted I could email you all my Kate configuration files and you could compare their settings with yours. Warning my Kate files have been massively reworked so they might not look much like yours... <grin> Keith

On 18 January 2012 14:33, /dev/ammo42 &lt;mickeytintincolle(a)yahoo.fr&gt; wrote: In a normal company, users come first. In open source, we all pretend users come first. Remember nobody gets paid to develop trinity. What it boils down to is "itching your own scratch". Say Darrell is having troubles with kate, or wants to implement something new with kate. Then he is likely to do it. He is not likely to develop a plasma interface because he doesn't care about it. Thats how I see it at least.

I tried those settings. No luck. I also tried --use in View_source.editor.args. No luck. I'm using FF 3.6.24. I understand. And thanks. I just want FF and kate to work the way I want. :) Yes, a lot of hammering, screaming and kicking, which is absurd. No software should be that cantankerous or difficult to configure. I am using the --use parameter in all shortcuts and *.desktop files, and like you, eventually tamed kate to my liking. Yet I can't get FF to use the same window that is already open. Darrell

Darrell Anderson wrote: Ah I understand now. It seems I hadn't understood you correctly. What I would recommend then is writing a small shell script and make it write out all it's arguments to a file. Then call that script from Firefox and watch how Firefox exactly calls the script. The problem should become visible then. You could also call kate with the right arguments from this script at some point if you cannot find another solution. Julius