[arch-general] ncmpcpp 0.6beta2-1
Hi, Since the upgrade of nmcpcpp to 0.6beta2 yesterday, custom keybindings no longer work, and the commandline subcommands (most importantly for me, `ncmpcpp toggle`) have stopped working as well. Downgrading to 0.5.10 solve these issues. Perhaps the package should stay at the last stable release? (I should say I don't follow ncmpcpp development closely at all, and for all I know that beta might have been around for years. In any case, I'm seeing the above problems with the beta version.) Cheers, Manolo --
On 14/09, Manolo Martínez wrote:
Hi,
Since the upgrade of nmcpcpp to 0.6beta2 yesterday, custom keybindings no longer work, and the commandline subcommands (most importantly for me, `ncmpcpp toggle`) have stopped working as well. Downgrading to 0.5.10 solve these issues.
Perhaps the package should stay at the last stable release? (I should say I don't follow ncmpcpp development closely at all, and for all I know that beta might have been around for years. In any case, I'm seeing the above problems with the beta version.)
Cheers, Manolo
-- Hi Manolo,
I discovered the same thing when I upgraded ncmpcpp yesterday. Then I made some searches and discovered the following: - the key bindings functionality has been redesign so as to use a bindings file located at /usr/share/doc/ncmpcpp which may be copied to your $XDG_CONFIG_HOME directory and then amended to suit your needs. See the NEWS file for more details. - the play, stop, pause, toggle, etc... command line arguments has been removed on purpose. See [1]. The workaround I am using now is to install mpc [2] and use it in all my scripts that was using the related ncmpcpp's command line argument [1]:http://bugs.musicpd.org/view.php?id=4013 [2]:https://www.archlinux.org/packages/?name=mpc Cheers, ___________________________ tlux <tlux@ghelew.ch>
On Mon, Sep 15, 2014 at 12:14 AM, tlux <tlux@ghelew.ch> wrote:
- the key bindings functionality has been redesign so as to use a bindings file located at /usr/share/doc/ncmpcpp which may be copied to your $XDG_CONFIG_HOME directory and then amended to suit your needs.
Except ncmpcpp does not use XDG_CONFIG_HOME Anyway, everything one needs to know is in the man page and example config files. RTFM is the best advice for OP.
On 09/15/14 at 12:34am, lolilolicon wrote:
On Mon, Sep 15, 2014 at 12:14 AM, tlux <tlux@ghelew.ch> wrote:
- the key bindings functionality has been redesign so as to use a bindings file located at /usr/share/doc/ncmpcpp which may be copied to your $XDG_CONFIG_HOME directory and then amended to suit your needs.
Except ncmpcpp does not use XDG_CONFIG_HOME
Anyway, everything one needs to know is in the man page and example config files. RTFM is the best advice for OP.
From the manual (which I did read prior to asking):
"When ncmpcpp starts, it tries to read user's keybindings from ~/.ncmpcpp/keys file. If no user's keybindings is found, ncmpcpp uses its default keybindings. An example keybindings file containing all default values is provided with ncmpcpp and can be found usually in /usr/share/doc/ncmpcpp (exact location may depend on used distribution/OS/configure prefix)." This hasn't changed from earlier versions, or at least I do have a ~/.nmcpcpp/keys file, which was, and isn't, correctly read. Manolo
On Mon, Sep 15, 2014 at 1:38 AM, Manolo Martínez <manolo@austrohungaro.com> wrote:
From the manual (which I did read prior to asking):
"When ncmpcpp starts, it tries to read user's keybindings from ~/.ncmpcpp/keys file. If no user's keybindings is found, ncmpcpp uses
Ah, you use ~/.ncmpcpp/bindings instead now. The manual hasn't been properly updated yet. My bad. It's mentioned in the NEWS file though...
On 15/09, lolilolicon wrote:
On Mon, Sep 15, 2014 at 12:14 AM, tlux <tlux@ghelew.ch> wrote:
- the key bindings functionality has been redesign so as to use a bindings file located at /usr/share/doc/ncmpcpp which may be copied to your $XDG_CONFIG_HOME directory and then amended to suit your needs.
Except ncmpcpp does not use XDG_CONFIG_HOME
Anyway, everything one needs to know is in the man page and example config files. RTFM is the best advice for OP.
True, I've put all my config files in XDG_CONFIG_HOME and I forgot that ncmpcpp doesn't use it. I have indeed RTFMs but I didn't catch the fact that some command line arguments were removed. Thank you for your constructive reply. ___________________________ tlux <tlux@ghelew.ch>
On Mon, Sep 15, 2014 at 1:59 AM, tlux <tlux@ghelew.ch> wrote:
Thank you for your constructive reply.
Is this sarcasm? I do think beta software can be destructive, though.
Thanks a lot for the info!
- the play, stop, pause, toggle, etc... command line arguments has been removed on purpose. See [1]. The workaround I am using now is to install mpc [2] and use it in all my scripts that was using the related ncmpcpp's command line argument
[1]:http://bugs.musicpd.org/view.php?id=4013 [2]:https://www.archlinux.org/packages/?name=mpc
I was hoping this was some kind of oversight... Well, too bad. I guess I'll have to start using another client, as you say. Cheers, Manolo
participants (3)
-
lolilolicon
-
Manolo Martínez
-
tlux