When Kate is already open, and in Firefox I press Ctrl-U to open the web page in the assigned external text editor (Kate), the web content opens in a second Kate session.
I want to use the current session only. I'm an MDI kind of person. :)
Editing the Firefox preferences to "kate --use" then causes Firefox to open the web page content in the Firefox viewer rather than Kate.
All of my kate related *.desktop files are set to kate --use.
Any ideas how to fix this?
Darrell
When Kate is already open, and in Firefox I press Ctrl-U to open the web page in the assigned external text editor (Kate), the web content opens in a second Kate session.
I want to use the current session only. I'm an MDI kind of person. :)
Editing the Firefox preferences to "kate --use" then causes Firefox to open the web page content in the Firefox viewer rather than Kate.
All of my kate related *.desktop files are set to kate --use.
Any ideas how to fix this?
Anybody?
Darrell
On 17 January 2012 21:04, Darrell Anderson humanreadable@yahoo.com wrote:
When Kate is already open, and in Firefox I press Ctrl-U to open the web page in the assigned external text editor (Kate), the web content opens in a second Kate session.
I want to use the current session only. I'm an MDI kind of person. :)
Editing the Firefox preferences to "kate --use" then causes Firefox to open the web page content in the Firefox viewer rather than Kate.
All of my kate related *.desktop files are set to kate --use.
Any ideas how to fix this?
Anybody?
Darrell
Seconded.
In general, Can I force kate to ONLY use one window?
we need a way to always to it :-)
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
On Tue, Jan 17, 2012 at 10:43 PM, Darrell Anderson humanreadable@yahoo.com 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@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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
Le mercredi 18 janvier 2012, Keith Daniels a écrit :
I use sessions heavily and like them a lot. So please don't make them go away...
----------- +1
Hi everybody,
I think that Darrell's question:
Is anybody interested?
should be asked on the "User's" list. Like implied questions related to TDE icones (thread "[trinity-devel] Trinity logo?"), for exemple.
I believe that KDE4 - Trinity are what we know because the KDE develpers did not listen or simply ask the user's opinion. They simply believed that their way of thinking was the best. This is the trap we (!) should not fall in!
Patrick
On Wed, Jan 18, 2012 at 9:07 AM, Patrick Serru patrick@serru.net wrote:
Le mercredi 18 janvier 2012, Keith Daniels a écrit :
I use sessions heavily and like them a lot. So please don't make them go away...
+1
Hi everybody,
I think that Darrell's question:
Is anybody interested?
should be asked on the "User's" list. Like implied questions related to TDE icones (thread "[trinity-devel] Trinity logo?"), for exemple.
I believe that KDE4 - Trinity are what we know because the KDE develpers did not listen or simply ask the user's opinion. They simply believed that their way of thinking was the best. This is the trap we (!) should not fall in!
Patrick
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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
I use sessions heavily and like them a lot. So
please don't make them go
away...
+1
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.
I'm not a developer. Just a packager and the person around here who tests most things beyond normal to find breakage. :)
I have no sway or technical ability to revert kate back to the good old days of using projects and the MDI. So be at peace. :)
With that said, kate sessions are broken. I filed some bug reports/enhancement requests about kate. When the bugzilla returns tomorrow I should update those reports.
I don't use sessions. I'm not a hard core developer to where I would see sessions being useful. I am an MDI person. I might have a dozen files open at any one time in kate, but never in a manner that would encourage me to use sessions. Possibly some day after I better learn C++ I might be different, but I suspect then I will have learned to use tdevelop. :)
I have the stupid --use flag set everywhere but kate remains broken.
I tried Keith's recommendation to set some Firefox options, but kate still opens in a separate window/session. I like the MDI and want Kate to open in the currently existing window.
Kate focus is broken. I can get kate to come forward but kate won't grab the focus. Bug report filed some time ago. This is a serious usability issue because despite appearing to have the focus because of popping forward, the user starts typing or performing mouse operations not on kate but in the app that has the focus. I've tried various focus settings to no avail.
All I want is kate to always perform in MDI mode and to correctly grab the focus when popping to the front. I'm open to the idea that there is some magical "just right" combination of settings that will provide this. I won't be embarrased to learn those settings --- just happy. :)
Darrell
Le mercredi 18 janvier 2012, Keith Daniels a écrit :
Please consider what Patrick is saying.
Keith
--------------------------------------------------------------------- (((-: 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
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...
I use kwrite as well for quick and dirty editing of simple text files. :) I have the *.txt mimetype associated with kwrite. I have all programming language mimetypes associated with kate.
Firefox is unique in that the user has to specify the external editor to use. There is no mimetype association per se like the files opened through konqueror. Changing that external editor in Firefox to kwrite will open the web page in kwrite rather than kate. For me that would result in the result in the same behavior: two editors open in two different windows. :)
Darrell
On 18 January 2012 12:41, Darrell Anderson humanreadable@yahoo.com wrote:
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...
I use kwrite as well for quick and dirty editing of simple text files. :) I have the *.txt mimetype associated with kwrite. I have all programming language mimetypes associated with kate.
Firefox is unique in that the user has to specify the external editor to use. There is no mimetype association per se like the files opened through konqueror. Changing that external editor in Firefox to kwrite will open the web page in kwrite rather than kate. For me that would result in the result in the same behavior: two editors open in two different windows. :)
Darrell
Would the problem be solved with a configuration option to always use the current session?
Firefox is unique in that the user has to specify the external editor to use. There is no mimetype association per se like the files opened through konqueror. Changing that external editor in Firefox to kwrite will open the web page in kwrite rather than kate. For me that would result in the result in the same behavior: two editors open in two different windows. :)
Would the problem be solved with a configuration option to always use the current session?
Maybe. Please provide more details. :)
Seems the --use parameter is supposed to do that,but if I follow you, then a configuration option would eliminate the requirement to use that parameter. The --use parameter would remain but a katerc option would force everything to open in the current session window. That would much better simulate the MDI.
I have copies of the 3.4.3 and 3.5.0 kdelibs and kdebase sources, if that would help.
Before we travel that tempting trail, first we need to verify whether this Firefox problem is repeatable with other users. I will not be embarrassed if the problem is at my end because of some oddball configuration.
Second, we should try to resolve bug report 692 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=692) because there might be a relationship with this Firefox bug.
Darrell
On Wed, Jan 18, 2012 at 1:18 PM, Darrell Anderson humanreadable@yahoo.com wrote:
Firefox is unique in that the user has to specify the external editor to use. There is no mimetype association per se like the files opened through konqueror. Changing that external editor in Firefox to kwrite will open the web page in kwrite rather than kate. For me that would result in the result in the same behavior: two editors open in two different windows. :)
Would the problem be solved with a configuration option to always use the current session?
Maybe. Please provide more details. :)
Seems the --use parameter is supposed to do that,but if I follow you, then a configuration option would eliminate the requirement to use that parameter. The --use parameter would remain but a katerc option would force everything to open in the current session window. That would much better simulate the MDI.
I have copies of the 3.4.3 and 3.5.0 kdelibs and kdebase sources, if that would help.
Before we travel that tempting trail, first we need to verify whether this Firefox problem is repeatable with other users. I will not be embarrassed if the problem is at my end because of some oddball configuration.
Second, we should try to resolve bug report 692 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=692) because there might be a relationship with this Firefox bug.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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 Wed, 18 Jan 2012 09:07:50 -0500 Patrick Serru patrick@serru.net wrote:
Le mercredi 18 janvier 2012, Keith Daniels a écrit :
I use sessions heavily and like them a lot. So please don't make them go away...
+1
Hi everybody, I think that Darrell's question:
Is anybody interested?
should be asked on the "User's" list. Like implied questions related to TDE icones (thread "[trinity-devel] Trinity logo?"), for exemple.
I believe that KDE4 - Trinity are what we know because the KDE
develpers did not listen or simply ask the user's opinion. They simply believed that their way of thinking was the best. This is the trap we (!) should not fall in!
Which users' opinion ? KDE developers are KDE users, so their opinion count. Moreover most functionality has been preserved going from KDE3 to KDE4, and KDE4 could be extended to enable KDE3's old but readable look. I'm actually surprised nobody did a KDE3-like Plasma theme. In the meantime, many people including myself find that KDE4 is a great desktop, at least when it doesn't crash (and it never does on my machine on which I use it) and once the insane defaults are changed.
Patrick
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 18 January 2012 14:33, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
On Wed, 18 Jan 2012 09:07:50 -0500 Patrick Serru patrick@serru.net wrote:
Le mercredi 18 janvier 2012, Keith Daniels a écrit :
I use sessions heavily and like them a lot. So please don't make them go away...
+1
Hi everybody, I think that Darrell's question:
Is anybody interested?
should be asked on the "User's" list. Like implied questions related to TDE icones (thread "[trinity-devel] Trinity logo?"), for exemple.
I believe that KDE4 - Trinity are what we know because the KDE
develpers did not listen or simply ask the user's opinion. They simply believed that their way of thinking was the best. This is the trap we (!) should not fall in!
Which users' opinion ? KDE developers are KDE users, so their opinion count. Moreover most functionality has been preserved going from KDE3 to KDE4, and KDE4 could be extended to enable KDE3's old but readable look. I'm actually surprised nobody did a KDE3-like Plasma theme. In the meantime, many people including myself find that KDE4 is a great desktop, at least when it doesn't crash (and it never does on my machine on which I use it) and once the insane defaults are changed.
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.
On Wed, 18 Jan 2012 14:39:44 -0500 Calvin Morrison mutantturkey@gmail.com wrote:
On 18 January 2012 14:33, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
On Wed, 18 Jan 2012 09:07:50 -0500 Patrick Serru patrick@serru.net wrote:
Le mercredi 18 janvier 2012, Keith Daniels a écrit :
I use sessions heavily and like them a lot. So please don't make them go away...
+1
Hi everybody, I think that Darrell's question:
Is anybody interested?
should be asked on the "User's" list. Like implied questions related to TDE icones (thread "[trinity-devel] Trinity logo?"), for exemple.
I believe that KDE4 - Trinity are what we know because the
KDE develpers did not listen or simply ask the user's opinion. They simply believed that their way of thinking was the best. This is the trap we (!) should not fall in!
Which users' opinion ? KDE developers are KDE users, so their opinion count. Moreover most functionality has been preserved going from KDE3 to KDE4, and KDE4 could be extended to enable KDE3's old but readable look. I'm actually surprised nobody did a KDE3-like Plasma theme. In the meantime, many people including myself find that KDE4 is a great desktop, at least when it doesn't crash (and it never does on my machine on which I use it) and once the insane defaults are changed.
In a normal company, users come first.
In open source, we all pretend users come first.
Developers are generally users so this is true, for a restricted class of users ;)
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.
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 tried those settings. No luck. I also tried --use in View_source.editor.args. No luck. I'm using FF 3.6.24.
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 understand. And thanks. I just want FF and kate to work the way I want. :)
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...
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
The --use parameter is supposed to force only one window.
That parameter works, but not with my problem description with Firefox. Could be something awry on my system as I customize my desktop like crazy. I'll have to test further in my testing account with a fresh profile, etc.
Darrell
--- On Tue, 1/17/12, Calvin Morrison mutantturkey@gmail.com wrote:
From: Calvin Morrison mutantturkey@gmail.com Subject: Re: [trinity-devel] Configuring Kate To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, January 17, 2012, 8:19 PM
On 17 January 2012 21:04, Darrell Anderson humanreadable@yahoo.com wrote:
When Kate is already open,
and in
Firefox I press Ctrl-U to open the web page in the
assigned
external text editor (Kate), the web content opens in
a
second Kate session.
I want to use the current session only. I'm an MDI
kind of
person. :)
Editing the Firefox preferences to "kate
--use" then causes
Firefox to open the web page content in the Firefox
viewer
rather than Kate.
All of my kate related *.desktop files are set to
kate
--use.
Any ideas how to fix this?
Anybody?
Darrell
Seconded.
In general, Can I force kate to ONLY use one window?
we need a way to always to it :-)
Darrell Anderson wrote:
When Kate is already open, and in Firefox I press Ctrl-U to open the web page in the assigned external text editor (Kate), the web content opens in a second Kate session.
I want to use the current session only. I'm an MDI kind of person. :)
Maybe using kwrite instead of kate would work in your case? The actual KParts are the same, it's just that kwrite lacks some things like multiple sessions.
Good luck! Julius
When Kate is already open, and in Firefox I press
Ctrl-U to open the web page in the assigned external text editor (Kate), the web content opens in a second Kate session.
I want to use the current session only. I'm an MDI
kind of person. :)
Maybe using kwrite instead of kate would work in your case? The actual KParts are the same, it's just that kwrite lacks some things like multiple sessions.
kwrite is strictly SDI. If I wanted to open several web pages I would end up with several instances of kwrite open. Yes, there is task bar grouping but that only reduces clutter in the task bar. The idea of using kate is opening everything in one window. kate has a nice document listing to the left side and I can traverse through any of the open documents.
kate works most of the time that way, but not all of the time.
Darrell
Darrell Anderson wrote:
When Kate is already open, and in Firefox I press
Ctrl-U to open the web page in the assigned external text editor (Kate), the web content opens in a second Kate session.
I want to use the current session only. I'm an MDI
kind of person. :)
Maybe using kwrite instead of kate would work in your case? The actual KParts are the same, it's just that kwrite lacks some things like multiple sessions.
kwrite is strictly SDI. If I wanted to open several web pages I would end up with several instances of kwrite open. Yes, there is task bar grouping but that only reduces clutter in the task bar. The idea of using kate is opening everything in one window. kate has a nice document listing to the left side and I can traverse through any of the open documents.
kate works most of the time that way, but not all of the time.
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