Mantas Mikulėnas
Mantas Mikulėnas
> Last time we added keycodes: [d13803f](https://github.com/neovim/neovim/commit/d13803f64fc5607c6319087240e35a8b86082f64) ~Okay, so looking at this, I assume I could add `case K_FIND: ... return VTERM_KEY_HOME` in terminal.c to permanently?~ (That didn't work.) After...
mpDris2 never grabs key events directly; `org.gnome.SettingsDaemon.MediaKeys` via DBus is the only interface it supports. However, In GNOME 3.10, if no players have registered with gnome-settings-daemon for media keys, g-s-d...
They *could* be ignored – the reason for hiding that under the command line option is that I'm not sure if there's a good way to distinguish "always present" weird...
So install a Python 3-compatible `mpd` module?
You don't – the command is only for testing whether Python _can_ import that module. For Python 3.6, you will need to install [python-mpd2](https://pypi.python.org/pypi/python-mpd2) ([git](https://github.com/Mic92/python-mpd2)).
Will try, but I'm not sure if this is really useful – given that the mpd protocol is clear-text (not encrypted), and many clients even read it from an environment...
At its core, mpDris2 is a translator between the MPD protocol and the D-Bus based MPRIS protocol. There's nothing GNOME-related or even systemd-related in that. So yes, it'll run fine...
No, especially not in 3.18+ where it completely depends on gnome-shell. Why do you need gnome-settings-daemon specifically? If you need hotkeys on a general X11 session, install xbindkeys/sxhkd and bind...
In the earlier `@deliver-to=foo PRIVMSG foobar` and `@deliver-to=foo PRIVMSG *` ideas, the latter would multicast to all matching clients... In XMPP, if I remember correctly, a message send to `foo@bar`...