| |||||||||||||
KRunner and GNOME Do: the run command evolvesKRunner and GNOME Do: the run command evolvesPosted Feb 12, 2009 18:59 UTC (Thu) by droundy (subscriber, #4559)In reply to: KRunner and GNOME Do: the run command evolves by clugstj Parent article: KRunner and GNOME Do: the run command evolves
It's very hard to use bash in combination with graphical programs. e.g. how do you view a pdf file in bash? After you view it, how do you open another program? Using bash isn't a nice alternative to something that always intercepts keystrokes (e.g. is integrated into a window manager or an application like Do or Krunner).
(Log in to post comments)
KRunner and GNOME Do: the run command evolves Posted Feb 13, 2009 17:19 UTC (Fri) by vmole (guest, #111) [Link] e.g. how do you view a pdf file in bash? There are a variety of choices, but I typically use "evince foo.pdf &". I'm not sure why this is harder than KRunner et. al.
KRunner and GNOME Do: the run command evolves Posted Feb 19, 2009 2:03 UTC (Thu) by SEMW (guest, #52697) [Link]
> I'm not sure why this is harder than KRunner et. al.
Keypresses? Given that both both Do and KRunner integrate with indexing frameworks, so can show a pdf anywhere on your system, I would only have to type "foo<enter>" (4 letters) for Do/KR to get the equivalent of typing "locate output.pdf | xargs evince &<enter>" (36 characters) in bash, a factor of 9 difference.
KRunner and GNOME Do: the run command evolves Posted Feb 19, 2009 4:55 UTC (Thu) by vmole (guest, #111) [Link] More likely "evince `locate output.pdf`&" (yes, fragile and doesn't handle locate errors), and far more likely I know which file I want and can use tab completion (yes, I know it works in Krunner et. al. as well) to save key strokes, but yeah, that's a point.
|
|||||||||||||