[kde] Re: How to use Plasmoid shortcuts
Dotan Cohen posted on Thu, 24 Feb 2011 02:08:07 +0200 as excerpted: > On Wed, Feb 23, 2011 at 20:14, Duncan <1i5t5.dun...@cox.net> wrote: >> Dotan Cohen posted on Wed, 23 Feb 2011 19:00:00 +0200 as excerpted: >> >>> I have the Quick Launch plasmoid in a panel. I have set it a keyboard >>> shortcut, but pressing that shortcut does not focus the plasmoid. How >>> are these shortcuts to be used? >> >> I don't claim any authority on this, but based on my observations... >> >> Plasmoid keyboard shortcuts should make the plasmoid visible... bring >> the panel to the top or unhide it if it's hidden, etc. >> What plasmoid shortcuts do beyond "make visible" appears to be >> individual plasmoid dependent. >> I suspect that quicklaunch, being primarily icon based interaction, >> doesn't do much beyond become visible when the shortcut is triggered. >> I'd consider it relatively unlikely that keyboard navigation >> implementation would be any sort of priority (other than "bluesky"), >> the assumption being that you use the right tool for the job, and while >> quicklaunch may indeed be a useful tool for point-n-click launching, >> it'd make a poor keyboard launcher even if the functionality was >> implemented. > Like you, I prefer to launch with a keyboard launcher. I usually use > Krunner (Alt-F2). However, because of a bug I cannot launch some apps > with it: > https://bugs.kde.org/show_bug.cgi?id=263883 I believe part of the issue may be that krunner checks more than just the shell-path. In particular, it knows of and ranks higher in the priority sequence anything found in the the apps menu (kickoff/kmenu/lancelot). If it sees more than one choice, it should have a list (you may have to expand the krunner window vertically, or look for the arrow, to cycle thru items not fitting in the list). If the nepomuk runner plugin is enabled and it's looking in mail, etc, as well, you can get a whole SLEW of generally false-positives, so turning that and a few others off if you never use their supplied choices can be useful. (Plus, at least in kde 4.5 and previous, the nepomuk plugin tended to crash krunner once in awhile, so turning it off increased krunner stability. IDK if that still applies with 4.6.) You can use the icons presented with the run-choices to determine the type of item. A nice app icon indicates that it's using the menu entry, with its associated icon. A generic "gear" icon indicates that it's pointing directly at a binary. What I suspect is happening is that you have a firefox menu entry which points to the system firefox (bypassing your ~/.bin/firefox entry). That has the nice fancy firefox icon since it's associated with the menu entry which includes it, so you can tell it's the menu entry. Lower down the rankings, you should find probably two "gear" icon choices, one for your ~/.bin/firefox entry, and another for the system firefox binary. Presumably, they'll be in path order. You have a couple choices to modify this (beyond turning off unnecessary krunner plugins as mentioned above). First, you can edit your firefox menu entry (context-click on the menu plasmoid and choose edit applications, that's the 4.6 wording, AFAIK it was slightly different in earlier versions, or simply run kmenuedit) to point to the ~/.bin/firefox instead of the system firefox. Second, you can either rename your ~/.bin/firefox entry to something unique (firefx, fx, ffox, whatever), or create a uniquely named symlink in the same dir to the existing firefox entry. Suppose you choose ffox. Hopefully, that won't conflict with anything else, or if it does, the other entries will be ranked lower in krunner, so typing ffox in krunner will get you the desired ~/.bin/ override. Meanwhile, kde/krunner path... Try this (in krunner) to see what settings kde/krunner are actually getting: env > ~/krunner.env Then open the file in a text editor to see the results. Since env is a separate app, that doesn't invoke the shell init files as konsole does, so you get the environment directly as krunner sees it. FWIW, kde, including krunner, gets my custom environment, including path, here, and with ~/bin coming before pretty much anything else in the path, as expected, it allows me to override (or more often, setup additional custom environment before launching) system binaries. I know there was a thread on that, but I suspect it might well be working as it does here, because I login at the CLI, then run "k" (actually, generally ". k", so it logs out the existing CLI login after starting), a custom script which: # Set/export some kde and xdg specific vars as so (see KDE User Guide # (from the khelpcenter package), Part VI, KDE for Administrators, Chapter # 25, KDE Internals, Environment variables subheading), because I don't # like the defaults: export KDE_NO_IPV6=1 export KDE_UTF8_FILENAMES=1 export KDEHOME="$HOME/kde" export KDETMP="/tmp/tmp-$USER/kde" export KDEVARTMP="$HOME/conf
[kde] Re: How to use Plasmoid shortcuts
On Wed, Feb 23, 2011 at 20:14, Duncan <1i5t5.dun...@cox.net> wrote: > Dotan Cohen posted on Wed, 23 Feb 2011 19:00:00 +0200 as excerpted: > >> I have the Quick Launch plasmoid in a panel. I have set it a keyboard >> shortcut, but pressing that shortcut does not focus the plasmoid. How >> are these shortcuts to be used? > > I don't claim any authority on this, but based on my observations... > > Plasmoid keyboard shortcuts should make the plasmoid visible... bring the > panel to the top or unhide it if it's hidden, etc. (I'm not sure about > desktop plasmoids, whether they trigger desktop activation or not, as I > run a dual monitor setup with one as the "working" display which doesn't > have much on it as it's often covered and the other as aux, generally > uncovered already to a large extent -- maximize only maximizes to the > active one, thus, to the "working" display in most cases. Thus, I haven't > really tried shortcuts on desktop plasmoids.) > > What plasmoid shortcuts do beyond "make visible" appears to be individual > plasmoid dependent. For menu type plasmoids, the ones I have shortcuts > attached to, it generally activates the menu (be that kickoff, the classic > menu, whatever... I have both setup here as I use the classic menu for its > bookmarks and kcontrol-applet menus, tho I don't actually use kickoff much > except for apps I seldom use, as I have a scripted hotkey-launcher I use > for most launching). For many others, simply making the plasmoid viewable > is the primary goal as they're primarily informational displays with > limited interactivity. > > I suspect that quicklaunch (which I don't normally use tho I played around > with it for this post, because as I said my preferred method for launching > frequently used apps is a scripted keyboard-shortcut based launcher, FWIW > my own script), being primarily icon based interaction, doesn't do much > beyond become visible when the shortcut is triggered. In theory, it could > "focus", allowing arrow-n-enter based navigation, triggering the > individual icon launchers, but I'd consider it relatively unlikely that > keyboard navigation implementation would be any sort of priority (other > than "bluesky"), the assumption being that you use the right tool for the > job, and while quicklaunch may indeed be a useful tool for point-n-click > launching, it'd make a poor keyboard launcher even if the functionality > was implemented. > Like you, I prefer to launch with a keyboard launcher. I usually use Krunner (Alt-F2). However, because of a bug I cannot launch some apps with it: https://bugs.kde.org/show_bug.cgi?id=263883 > So... if you're looking for a plasmoid (or other tool) to take focus and > allow keyboard interactive launching... use something other than > quicklaunch... and without active keyboard navigation implemented in > quicklaunch, "make-visible" is about the best one can expect from a > trigger shortcut assigned to it. > I'll file a feature request on the arrows-navigation on the plasmoid, like you mentioned. That is quite the behaviour that I had expected. -- Dotan Cohen http://gibberish.co.il http://what-is-what.com ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: How to use Plasmoid shortcuts
Dotan Cohen posted on Wed, 23 Feb 2011 19:00:00 +0200 as excerpted: > I have the Quick Launch plasmoid in a panel. I have set it a keyboard > shortcut, but pressing that shortcut does not focus the plasmoid. How > are these shortcuts to be used? I don't claim any authority on this, but based on my observations... Plasmoid keyboard shortcuts should make the plasmoid visible... bring the panel to the top or unhide it if it's hidden, etc. (I'm not sure about desktop plasmoids, whether they trigger desktop activation or not, as I run a dual monitor setup with one as the "working" display which doesn't have much on it as it's often covered and the other as aux, generally uncovered already to a large extent -- maximize only maximizes to the active one, thus, to the "working" display in most cases. Thus, I haven't really tried shortcuts on desktop plasmoids.) What plasmoid shortcuts do beyond "make visible" appears to be individual plasmoid dependent. For menu type plasmoids, the ones I have shortcuts attached to, it generally activates the menu (be that kickoff, the classic menu, whatever... I have both setup here as I use the classic menu for its bookmarks and kcontrol-applet menus, tho I don't actually use kickoff much except for apps I seldom use, as I have a scripted hotkey-launcher I use for most launching). For many others, simply making the plasmoid viewable is the primary goal as they're primarily informational displays with limited interactivity. I suspect that quicklaunch (which I don't normally use tho I played around with it for this post, because as I said my preferred method for launching frequently used apps is a scripted keyboard-shortcut based launcher, FWIW my own script), being primarily icon based interaction, doesn't do much beyond become visible when the shortcut is triggered. In theory, it could "focus", allowing arrow-n-enter based navigation, triggering the individual icon launchers, but I'd consider it relatively unlikely that keyboard navigation implementation would be any sort of priority (other than "bluesky"), the assumption being that you use the right tool for the job, and while quicklaunch may indeed be a useful tool for point-n-click launching, it'd make a poor keyboard launcher even if the functionality was implemented. So... if you're looking for a plasmoid (or other tool) to take focus and allow keyboard interactive launching... use something other than quicklaunch... and without active keyboard navigation implemented in quicklaunch, "make-visible" is about the best one can expect from a trigger shortcut assigned to it. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] How to use Plasmoid shortcuts
I have the Quick Launch plasmoid in a panel. I have set it a keyboard shortcut, but pressing that shortcut does not focus the plasmoid. How are these shortcuts to be used? Thanks! -- Dotan Cohen http://gibberish.co.il http://what-is-what.com ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Sound guru needed
On Tuesday 22 February 2011 19:42:22 Wouter Van Meir wrote: > What distribution do you use? > I had pulseaudio on kubuntu 10.10 but disabled it months ago, and > everything is still working (better than before, pulseaudio and me never > got along). > > This is how it goes (If I didn't forget anything): > # apt-get remove pulseaudio > > after that it falls back to alsa > > For stuff that's using gstreamer, like clementine, you need to have an > alsa plugin, ofcourse: > # apt-get install gstreamer0.10-alsa > # apt-get remove gstreamer0.10-pulseaudio > > just check what doesn't work yet and why, or report back:) I was wondering if that was the way to go. It will be another week or so before I get chance to try the device again, but I'll let you know how it goes. I can understand the logic behind pulseaudio, but at the moment I don't think it is of great benefit to me. I can always reinstall it if I think I need to. Anne -- New to KDE Software? - get help from http://userbase.kde.org signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
