This is more of a user question than developer but I'll post here because I use Kate all day to review build scripts, patches, source files, etc.
In my KDE 3.5.10 version of Kate I have been long able to use a kludge to keep Kate in MDI (multiple document interface) mode. That is, regardless of what I do, all documents I want to open in Kate all open in the same window. I never have more than one window of Kate open. I use the Documents list window and the tabbar plugin to identify my files.
Now that I am using Trinity too, I no longer can apply my kludge. Kate 3.5.13 is very much an SDI (single document interface) app and that frustrates me. I don't like multiple windows being open. Forced grouping does not really help.
I am struggling with multiple Kate windows. I get confused when I double-click on a file in Konqueror and the file opens in Yet Another Window of Kate rather than the one I have open. Seems the only way I can control this is to open all files from within Kate and that is inconvenient too.
How do I go about forcing all documents that I open in Kate to appear in the same window?
Second, is there a better Quick Launch button that just opens Kate? I dislike the popup menu where I have to select how I want Kate to open. To me the idea of Quick Launch buttons is one click.
Thanks.
Darrell
On Tue, Nov 22, 2011 at 5:18 PM, Darrell Anderson humanreadable@yahoo.com wrote:
This is more of a user question than developer but I'll post here because I use Kate all day to review build scripts, patches, source files, etc.
In my KDE 3.5.10 version of Kate I have been long able to use a kludge to keep Kate in MDI (multiple document interface) mode. That is, regardless of what I do, all documents I want to open in Kate all open in the same window. I never have more than one window of Kate open. I use the Documents list window and the tabbar plugin to identify my files.
Now that I am using Trinity too, I no longer can apply my kludge. Kate 3.5.13 is very much an SDI (single document interface) app and that frustrates me. I don't like multiple windows being open. Forced grouping does not really help.
I am struggling with multiple Kate windows. I get confused when I double-click on a file in Konqueror and the file opens in Yet Another Window of Kate rather than the one I have open. Seems the only way I can control this is to open all files from within Kate and that is inconvenient too.
How do I go about forcing all documents that I open in Kate to appear in the same window?
Second, is there a better Quick Launch button that just opens Kate? I dislike the popup menu where I have to select how I want Kate to open. To me the idea of Quick Launch buttons is one click.
Thanks.
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
Hi Darrell
Just to make sure I understand what you want... It sounds like you want to make Kate use a single session at all times... In other words when you open a Kate file with Konqueror or from the console it just adds that file to the existing, running instance of Kate:
If that is correct this should do what you want, at least it works for me. As far as I know, this works on KDE4 and KDE3 and probably all other programs that can use the %U command line argument
If starting Kate from the KDE menu use the Menu Editor to edit the Kate's "Command" text box. Insert '--use' between 'kate' and the '%U'. It should end up looking like this: Command: kate --use %U
You also need to edit this file: /home/$USER/.local/share/applications/kde4-kate.desktop and change the "Exec: " line to: Exec: kate --use %U
At this point you probably need to close all instances of Kate and then do the test below. Sometimes I have had to restart Xwindows to get Kate to pay attention to changes, so if it doesn't work, restart the computer before you give up.
Test the new configuration in Konqueror. If Konqueror gives you problems about not being able to open /usr/bin/kate, this is to a known bug in the KDE-Libs with DBUS. There is a workaround for this.
Edit the file: /home/$USER/.local/share/applications/kde4-kate.desktop and find the line "X-DBUS-StartupType=Multi" and change the "Multi" to "None".
I use a Kate icon in the toolbar panel. To get it to work correctly I had use the choice "configure Kate button" that you get when you right click over the icon. Then go to >> "Application" tab >> "Advanced Options" and change "DCOP registration" to None. My icon setup for calling Kate is not typical so you may not need to do this.
Keith
If starting Kate from the KDE menu use the Menu Editor to edit the Kate's "Command" text box. Insert '--use' between 'kate' and the '%U'. It should end up looking like this: Command: kate --use %U
You also need to edit this file: /home/$USER/.local/share/applications/kde4-kate.desktop and change the "Exec: " line to: Exec: kate --use %U
OK. Just did both. Seems I now have a single window/session. Much better than before. :) Yet now when I have Kate open and select a file from within Konqueror, the file opens in Kate but Kate will not snap to the front and gain focus. Kate flashes in the task bar/panel.
I changed the focus stealing prevention level from Low to None to get Kate to move to the front. I don't know how changing that option will affect other things I do.
I have that option set to Low for years and Kate always came forward. Please don't say "bug report." :)
I use a Kate icon in the toolbar panel. To get it to work correctly I had use the choice "configure Kate button" that you get when you right click over the icon. Then go to >> "Application" tab >> "Advanced Options" and change "DCOP registration" to None. My icon setup for calling Kate is not typical so you may not need to do this.
OK, I figured that out after I posted. Just create my own button. :)
Thanks!
Darrell
On Tue, Nov 22, 2011 at 7:21 PM, Darrell Anderson humanreadable@yahoo.com wrote:
If starting Kate from the KDE menu use the Menu Editor to edit the Kate's "Command" text box. Insert '--use' between 'kate' and the '%U'. It should end up looking like this: Command: kate --use %U
You also need to edit this file: /home/$USER/.local/share/applications/kde4-kate.desktop and change the "Exec: " line to: Exec: kate --use %U
OK. Just did both. Seems I now have a single window/session. Much better than before. :) Yet now when I have Kate open and select a file from within Konqueror, the file opens in Kate but Kate will not snap to the front and gain focus. Kate flashes in the task bar/panel.
I changed the focus stealing prevention level from Low to None to get Kate to move to the front. I don't know how changing that option will affect other things I do.
I have that option set to Low for years and Kate always came forward. Please don't say "bug report." :)
I use a Kate icon in the toolbar panel. To get it to work correctly I had use the choice "configure Kate button" that you get when you right click over the icon. Then go to >> "Application" tab >> "Advanced Options" and change "DCOP registration" to None. My icon setup for calling Kate is not typical so you may not need to do this.
OK, I figured that out after I posted. Just create my own button. :)
Thanks!
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
Glad it helped. I too am a heavy long term Kate user, if you are interested, over the years I have created a lot of utility scripts for Kate for use with the "Filter Text" command. If you want copies tell me how to send the collection to you and I will. They are mostly sed based scripts for manipulating large amounts of text inside Kate.
RE: I changed the focus stealing prevention level from Low to None...
Where or how do you do that? Somehow I never found that in all the years I used KDE.
Keith
Glad it helped. I too am a heavy long term Kate user, if you are interested, over the years I have created a lot of utility scripts for Kate for use with the "Filter Text" command. If you want copies tell me how to send the collection to you and I will. They are mostly sed based scripts for manipulating large amounts of text inside Kate.
Whoa, I never got that smart with Kate. I keep telling myself I'm going to force myself to one day sit and learn how to use reg expressions in Kate to do proper searches. I never knew I could use sed directly in Kate. I always did that from a terminal window.
Just send by email if you want.
RE: I changed the focus stealing prevention level from Low to None...
Where or how do you do that? Somehow I never found that in all the years I used KDE.
Control Center, Desktop, Window Behavior, Advanced tab.
I submitted an enhancement request (Bug report 642) a few days ago to move the focus prevention option to the Focus tab. To me makes more sense there.
Darrell
Le 23/11/2011 00:47, Keith Daniels a écrit :
On Tue, Nov 22, 2011 at 5:18 PM, Darrell Anderson humanreadable@yahoo.com wrote:
This is more of a user question than developer but I'll post here because I use Kate all day to review build scripts, patches, source files, etc.
In my KDE 3.5.10 version of Kate I have been long able to use a kludge to keep Kate in MDI (multiple document interface) mode. That is, regardless of what I do, all documents I want to open in Kate all open in the same window. I never have more than one window of Kate open. I use the Documents list window and the tabbar plugin to identify my files.
Now that I am using Trinity too, I no longer can apply my kludge. Kate 3.5.13 is very much an SDI (single document interface) app and that frustrates me. I don't like multiple windows being open. Forced grouping does not really help.
I am struggling with multiple Kate windows. I get confused when I double-click on a file in Konqueror and the file opens in Yet Another Window of Kate rather than the one I have open. Seems the only way I can control this is to open all files from within Kate and that is inconvenient too.
How do I go about forcing all documents that I open in Kate to appear in the same window?
Second, is there a better Quick Launch button that just opens Kate? I dislike the popup menu where I have to select how I want Kate to open. To me the idea of Quick Launch buttons is one click.
Thanks.
Darrell
Hi Darrell
Just to make sure I understand what you want... It sounds like you want to make Kate use a single session at all times... In other words when you open a Kate file with Konqueror or from the console it just adds that file to the existing, running instance of Kate:
If that is correct this should do what you want, at least it works for me. As far as I know, this works on KDE4 and KDE3 and probably all other programs that can use the %U command line argument
If starting Kate from the KDE menu use the Menu Editor to edit the Kate's "Command" text box. Insert '--use' between 'kate' and the '%U'. It should end up looking like this: Command: kate --use %U
You also need to edit this file: /home/$USER/.local/share/applications/kde4-kate.desktop and change the "Exec: " line to: Exec: kate --use %U
At this point you probably need to close all instances of Kate and then do the test below. Sometimes I have had to restart Xwindows to get Kate to pay attention to changes, so if it doesn't work, restart the computer before you give up.
Test the new configuration in Konqueror. If Konqueror gives you problems about not being able to open /usr/bin/kate, this is to a known bug in the KDE-Libs with DBUS. There is a workaround for this.
Edit the file: /home/$USER/.local/share/applications/kde4-kate.desktop and find the line "X-DBUS-StartupType=Multi" and change the "Multi" to "None".
I use a Kate icon in the toolbar panel. To get it to work correctly I had use the choice "configure Kate button" that you get when you right click over the icon. Then go to >> "Application" tab >> "Advanced Options" and change "DCOP registration" to None. My icon setup for calling Kate is not typical so you may not need to do this.
I would add that basic information is here: help:/kate/fundamentals-using-sessions.html#old-behavior "Read the fabulous manual" ;-)
Here, kate is opened with TDM, kate is closed with TDM. All files are opened in the default session.
Only remaining problem for me: forgetting to save documents before closing TDM has caused TDM to enter an endless loop at closeup, several times. I needed to halt the system by another way. (It spent one whole night displaying "Saving your settings".)
Apparently I'm not out of the woods yet with Kate. With each new document that opens, my toolbar gets re-arranged. Is there a fix for this?
Darrell
On Wed, Nov 23, 2011 at 6:34 PM, Darrell Anderson humanreadable@yahoo.com wrote:
Apparently I'm not out of the woods yet with Kate. With each new document that opens, my toolbar gets re-arranged. Is there a fix for this?
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
Hi Darrell
Does it change to something different or does it just revert to what it was before you changed everything?
If it just refuses to save any changes, then no I have not found a fix for this. On my system Kate will no save settings between start ups.
I gave up and went in and edited the files that store the settings. I have not upgraded to 3.5.13 yet (still trying to figure out Arch and solve broken hardware problems) so I don't know if it is fixed there.
Keith
Does it change to something different or does it just revert to what it was before you changed everything?
If it just refuses to save any changes, then no I have not found a fix for this. On my system Kate will no save settings between start ups.
I gave up and went in and edited the files that store the settings. I have not upgraded to 3.5.13 yet (still trying to figure out Arch and solve broken hardware problems) so I don't know if it is fixed there.
The problem turned out to be something obscure. I have a $KDEDIRS directory on my system. For many years I stored my own revised *.desktop files there to fix problems in KDE3. Worked wonderfully all of these years.
As I mentioned previously, I have used a kludge of sorts to run Kate with the old Projects mode and MDI (multiple document interface). Basically I use kate and kde lib files from KDE 3.4.3 and amazingly, this has worked through 3.5.10. I knew with TDE I no longer would be able to do that. In preparation of starting to use TDE more often, I decided to end my Kate adventure and start using the sessions version.
After some methodical troubleshooting, eventually I remembered I had Kate configuration files, such as kateui.rc in my $KDEDIRS directory. These files were overriding anything I tried to do in Kate. I moved those files and then finally I could configure the Kate toolbars. The problem was these older config files worked for the older version of Kate and not the newer sessions version.
I saw some strange things during my troubleshooting. For example, with each new document I opened in Kate, the icon buttons in the Kate toolbar would shift left by one. You had to see this --- like the app was possessed. :)
Well, I just don't like Kate sessions. Long ago I submitted a bug report/enhancement request to provide the option of using Kate Projects and MDI rather than sessions and SDI. I can only hope. I have the old 3.4.3 code around here on some old Mandrake CDs I think.
I mentioned with the start options you provided me that Kate no longer would pop to the front and grab the focus unless I set focus stealing to none. Today I noticed a side effect of that. I open my virtual machines in virtual desktop 2 and now whenever I do that the focus shifts to that virtual desktop immediately. Not what I want because I prefer them to open in the background as they take a minute or two to fully boot. Annoying. Yet another reason not to like Kate sessions.
While surfing the web for clues about what was causing my momentary grief, I ran into threads and discussions about Kate. My observation of these discussions is that to this day, even in KDE 4.7.x, the Kate sessions model is broken and rarely functions the way anybody expects or wants.
Darrell
I mentioned with the start options you provided me that Kate no longer would pop to the front and grab the focus unless I set focus stealing to none. Today I noticed a side effect of that. I open my virtual machines in virtual desktop 2 and now whenever I do that the focus shifts to that virtual desktop immediately. Not what I want because I prefer them to open in the background as they take a minute or two to fully boot. Annoying. Yet another reason not to like Kate sessions.
There is a work-around:
In Control Center, Desktop, Window-Specific Settings; or from Kate's title bar context menu, select Advanced, Special window settings; and create an option for Kate. In the 'Workarounds' tab, set the focus stealing prevention level to None and leave the global setting at Low.
How in the world did I remember that? :)
Darrell
On Thu, Nov 24, 2011 at 11:20 PM, Darrell Anderson humanreadable@yahoo.com wrote:
Does it change to something different or does it just revert to what it was before you changed everything?
If it just refuses to save any changes, then no I have not found a fix for this. On my system Kate will no save settings between start ups.
I gave up and went in and edited the files that store the settings. I have not upgraded to 3.5.13 yet (still trying to figure out Arch and solve broken hardware problems) so I don't know if it is fixed there.
The problem turned out to be something obscure. I have a $KDEDIRS directory on my system. For many years I stored my own revised *.desktop files there to fix problems in KDE3. Worked wonderfully all of these years.
As I mentioned previously, I have used a kludge of sorts to run Kate with the old Projects mode and MDI (multiple document interface). Basically I use kate and kde lib files from KDE 3.4.3 and amazingly, this has worked through 3.5.10. I knew with TDE I no longer would be able to do that. In preparation of starting to use TDE more often, I decided to end my Kate adventure and start using the sessions version.
After some methodical troubleshooting, eventually I remembered I had Kate configuration files, such as kateui.rc in my $KDEDIRS directory. These files were overriding anything I tried to do in Kate. I moved those files and then finally I could configure the Kate toolbars. The problem was these older config files worked for the older version of Kate and not the newer sessions version.
I saw some strange things during my troubleshooting. For example, with each new document I opened in Kate, the icon buttons in the Kate toolbar would shift left by one. You had to see this --- like the app was possessed. :)
Well, I just don't like Kate sessions. Long ago I submitted a bug report/enhancement request to provide the option of using Kate Projects and MDI rather than sessions and SDI. I can only hope. I have the old 3.4.3 code around here on some old Mandrake CDs I think.
I mentioned with the start options you provided me that Kate no longer would pop to the front and grab the focus unless I set focus stealing to none. Today I noticed a side effect of that. I open my virtual machines in virtual desktop 2 and now whenever I do that the focus shifts to that virtual desktop immediately. Not what I want because I prefer them to open in the background as they take a minute or two to fully boot. Annoying. Yet another reason not to like Kate sessions.
While surfing the web for clues about what was causing my momentary grief, I ran into threads and discussions about Kate. My observation of these discussions is that to this day, even in KDE 4.7.x, the Kate sessions model is broken and rarely functions the way anybody expects or wants.
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
Thanks Darrell
I will check out some of those "obscure" issues. I might have done something like that myself...
Keith
-
Darrell Anderson -
Keith Daniels -
Laurent Dard