Klipper recognizes strings beginning with ~ as paths but it does not bother to normalize them before sending them to applications. Havoc ensues. Reproducible: Always Steps to Reproduce: 1. Select text [~/]. 2. Tell Klipper to open the location with Dolphin. 3. Select text [~/rpmbuild]. Actual Results: 1. Klipper lets you choose how to open the location. 2. Dolphin cannot find ~ in the home directory. 3. Klipper lets you choose how to open the location. Expected Results: 2. Let Dolphin display the home directory 3. Nothing, unless the home directory contains rpmbuild. Klipper normally does not react to selecting paths that do not correspond to items, such as /a/b/c. Dolphin cannot handle the invocation { dolphin '~/'; } but it is not required to. Klipper should have substituted $HOME before calling Dolphin to open it.
It's a cool idea, but given the lack of movement for so long, I think this is unlikely to be implemented unless someone submits a merge request to do it. Accordingly, I'm going to close this request so that the list of requested features better reflects work in progress or under active consideration. This doesn't mean that the idea is being vetoed, just that there aren't resources to consider implementing it absent volunteer contributions to do so--for which no formal feature request is needed. Thanks for understanding!