custom notification seem to be ignored

[Dirk Heilig]

According to man byobu, all i need to do to have a custom notification is:
put an executable into ~/.byobu/bin/ with a name schema like: 10_test
this don't seam to work for me.
i've tried it on different versions, even compiled the latest myself.

i've written a Dockerfile to reproduce this behavior:

RUN apt-get update && apt-get install -y tmux byobu locales-all
RUN useradd -ms /bin/bash me
USER me
RUN mkdir -p ~/.byobu/bin
RUN echo "#!/bin/bash" > ~/.byobu/bin/10_test
RUN echo "echo test" >> ~/.byobu/bin/10_test
RUN chmod +x ~/.byobu/bin/10_test
RUN byobu-enable
RUN ~/.byobu/bin/10_test | grep test # lets make sure this is executable and prints test
CMD /usr/bin/byobu

just build and run the container, or reproduce the steps yourself.

The notification does not appear, nor does it appear in the list of possible notifications in the menu (F9)

I'm not sure if this is an actual bug in the code or just incorrect or misleading documentation.

[Dustin Kirkland  (kirkland)]

Everything you did here is correct.

The only other thing you need to do is enable the "custom" notification itself (which is not enabled by default).

You can see the "#custom" commented out in /usr/share/byobu/status/status.

You'll need to enable that in your ~/.byobu/status file by copying (and editing) the notifications you want from /usr/share/byobu/status/status in ~/.byobu/status. For your custom notifications, just remove the "#" from "#custom".