Bug 164405 - Dbus property to get current url for Dolphin
Summary: Dbus property to get current url for Dolphin
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-18 22:07 UTC by peppelorum
Modified: 2021-03-09 02:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description peppelorum 2008-06-18 22:07:45 UTC
Version:           1.0.2 (using 4.0.5 (KDE 4.0.5), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-17-generic

I have made a small script so that F4 opens a new tab in Yakuake, if you are using Konqueror.
I have tried to make this possible with Dolphin as well but I can't find a dbus method for this.

So my wish is a property to get the current url.

You can find the small hack at:

http://www.kde-apps.org/content/show.php/Bind+F4%28open+terminal%29+to+Yakuake?content=30461
It hasn't been updated for a while so it just supports Konq for KDE3, KDE4 is in the works.

Best regards
Peppe Bergqvist
Comment 1 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:40 UTC
Resetting assignee to default as per bug #305719
Comment 2 Joan 2016-01-15 02:27:07 UTC
I voted for this bug (maybe it should be called a feature request) because it would be very useful to be able to get that information to be used in CLI or scripts. It would allow to make some useful decisions depending on what the current url is.

For instance, this information could be used to prevent local dolphin and/or system unwanted hangings when dealing with shared remote filesystem (un)mounts (for example, on unexpected NFS server shutdowns).
Comment 3 Justin Zobel 2021-03-09 02:18:31 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.