Adam Hunt

It seems to me that documenting the protocol adaptations/extensions would be the best way to encourage the developers of other clients to add support to their codebases. Ideally, I suppose...

I seem to be hitting this same bug. ``` [adam@Drogon]~/devel/go/src% lsp -------------------------------------------------------------------------------------------------------------------------------------- bazil.org dir(96 files) bitbucket.org dir(33 files) code.google.com dir(718 files) github.com dir(3699 files) golang.org dir(622 files) gopkg.in dir(85 files)...

I just ran into this little issue again. Have you given any further thought to a new mapping?

I'm experiencing almost exactly the same issue but I'm running F22-alpha. I also had to build the package myself as I was unable to get installed using the extensions site....

9P is another option.

I thought I'd chime in and say that a Wayland native version of [rofi](https://davedavenport.github.io/rofi/) would be ideal, at least in my opinion.

If someone decides to implement this feature please ensure that the notation allows for cases where an interface has multiple IPs bound to it. http://www.policyrouting.org/iproute2.doc.html#ss9.3 https://baturin.org/docs/iproute2/#Address%20management

It looks like this has been rectified. https://github.com/MediaBrowser/Emby.Common

I don't disagree; I was only commenting on the most recent issue.

Has any further thought been given to this patch?