Version: 3.96.00 (using KDE KDE 3.95.0) Installed from: Debian testing/unstable Packages Compiler: gcc 4.x (probably 4.1) OS: Linux In the Konqueror settings, under Web Shortcuts, there is a drop-down to select the delimiter for web shortcuts. I can select a space as the delimiter and click apply, but the setting isn't saved past that. After closing the settings, nothing has changed. The web shortmuts still expect a colon and not a space. Reopening the settings shows that colon is still selected. I am using the KDE4 beta packages in Debian experimental.
I can confirm this on a recent KDE4 SVN build.
Same here, using the SVN snapshot packages from OpenSUSE; the last update I performed was on 18 december.
And a quick update.. Manually changing the configuration file does work: The share/config/kuriikwsfilterrc has a line that says either: KeywordDelimiter=: or KeywordDelimiter=\s The \s is given when the setting is changed to 'space', but this doesn't work; when it is manually changed to KeywordDelimiter=32, space does work as a delimiter, and the settings dialog actually says that it has been changed to 'space'. This seems to suggest that either the setting is wrongly written to the configuration file, or that it incorrectly interprets the \s. Hope this helps.
Must change the UI. Space is not a valid possibility because it breaks krunner (minicli in KDE3).
I would really like it if space would work again. Space is nice precisely *because* it looks like a command. (I have shell aliases setup to do the same things as my web shortcuts, for example.) Also, it has the distinct advantage over ':' of not having to use the Shift key at all in most cases.
*** Bug 152753 has been marked as a duplicate of this bug. ***
152630 is a duplicate of this bug. I second comment #5 from Josh Berry : "space" as a delimiter is quick to type and looks like a standard command
*** Bug 152630 has been marked as a duplicate of this bug. ***
Created attachment 23374 [details] Workaround for this bug After trying to debug this bug, I found the problem is not in the kurifilter module, but somewhere in the KConfig. Attached is a proposed workaround for this problem.
I have the same bug on KDE trunk compiled from Gentoo overlay.
SVN commit 773002 by amantia: Make it possible to use SPACE as delimiter, like in KDE3 (we had the GUI, it just did not work). ":" works, even if SPACE is selected, so krunner will still work. BUG:153142 M +2 -1 ikwsopts.cpp M +1 -1 kuriikwsfiltereng.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=773002
*** Bug 155443 has been marked as a duplicate of this bug. ***
When the web shortcut delimiter is set to space, if I use Konqueror's search bar to google for some "keyword" I actually get a page with results for "gg:keyword". Here's a screenshot which may explain it better: http://img153.imageshack.us/img153/9326/86138391cw5.png Should I post a new bug?
Do you perchance have Google as default search engine set?
Gabriel, yes, Google is configured as default search engine. If I set web shortcut delimiter to "colon", then Konqueror search bar works as expected, without adding "gg:" infront of the search keyword.
Has the fix been backported to the 4.0 branch yet? With r779633 konqueror still does not remember the new shortcut delimiter and always defaults to the colon.
This bug is still present in 4.0.2 (packages from Kubuntu 8.04 beta).
Created attachment 26480 [details] Workaround for KDE4.1 I confirm this bug is still present in KDE4.1 when the space keyword delimiter is used. The attached patch should fix it.
As of KDE 4.1.2 this bug is still present. It seems that KConfig.readEntry() won't parse space as an int :-) --- cut --- Index: konq-plugins/searchbar/searchbar.cpp =================================================================== --- konq-plugins/searchbar/searchbar.cpp (revision 867761) +++ konq-plugins/searchbar/searchbar.cpp (working copy) @@ -103,7 +103,7 @@ if (s_delimiter == 0) { KConfig _config("kuriikwsfilterrc", KConfig::NoGlobals); KConfigGroup config(&_config, "General"); - s_delimiter = config.readEntry("KeywordDelimiter", int(':')); + s_delimiter = config.readEntry("KeywordDelimiter", QString(":")).at(0); } return s_delimiter; } --- cut ---
Is this bug fixed n KDE 4.2.0? I'm asking because I can reproduce it... Thanks.
On Kubuntu 8.10 with kde 4.2.0 I had to set the delimiter again (in the settings gui). So it's actually fixed, but needs