Bug 150778 - Konqueror keyword searches with the same words as kioslave namespaces fail to work
Summary: Konqueror keyword searches with the same words as kioslave namespaces fail to...
Status: RESOLVED INTENTIONAL
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-10-13 07:23 UTC by Russell Jones
Modified: 2011-06-12 23:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Russell Jones 2007-10-13 07:23:24 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Fedora RPMs

I'm trying to use Konqueror's keyword searches to make things overall easier to use.  For example, "perldoc <text>" as a keyword search forwards me to Perl's help center, essentially giving me the same information I could get by typing such a string into a terminal, but in a more convenient form.

This bug arose when I tried to do the same thing with "man", taking advantage of KDE's ioslaves to form a URI that fetches from the local manpage database.  I have a keyword search called "manpage", with URI keyword "man" that says to turn into "man:\{@}".  Effectively, this just means I should be able to use a space instead of the colon to generate a page such as "man wget", just as the terminal syntax would be, and saving a keystroke of Shift.

However, with that keyword search instituted, Konqueror fails to recognize it, turning "man wget" into an ordinary Google search for "man wget".  If the keyword trigger is changed to something else such as "manual", now it does work, but that isn't what I want since the whole point of having this keyword search is so that it can be triggered by simply "man" folowed by a space.

I tested it out with various other keywords, such as "remote", which made it clear: any keyword that's the same as a kioslave namespace doesn't work, and otherwise it does work.

Because kioslaves depend on a following colon and possibly some slashes to be recognized, I don't see any reason why they're causing conflicts with search words that are the same but without the colon.
Comment 1 Maksim Orlovich 2007-10-13 21:49:51 UTC
FYI, you can use #manpage. 

Comment 2 Jaime Torres 2008-10-12 12:35:16 UTC
I think there are two concepts mixed here:

The kioslaves that are called using the corresponding protocol part of the URI (protocol://URL)
and
The webshortcuts, where a prefix is used to do something more easy.

Maybe you could achieve to call a man page using man manpage with the webshortcuts.
Comment 3 Dawit Alemayehu 2011-06-12 23:02:15 UTC
man and info page is already supported and does not require you to enter web shortcut keys because KDE already provides an ioslave for it. It already provides automatic completion if you type man: in any KDE application that uses KUrlCompletion, e.g. konqueror. Even when that is not the case entering "man:/get" should work properly. As already stated in previous comment, there is already a shortcut you can use "#" for man pages and "##" for info pages.