maxhalford / chime Goto Github PK

Hey there, I love chime! I'm having troubles running it on a remote server. This is what I get when I call chime.info(sync=True, raise_error=True):

RuntimeError: Command 'aplay /home/mgrasso/miniconda3/envs/pyphi/lib/python3.7/site-packages/themes/zelda/info.wav' returned non-zero exit status 127. stderr: /bin/sh: 1: aplay: not found

Any tips? Thanks in advance,
MG

I have multiple sound cards in my computer, so I'd like a way to specify which card to play sounds with via chime. I've hacked in a fix that works for me, but I could see this being useful for others as well.

...
THEME = _get_default_theme(config_path, fallback_theme='chime')
RUN_ARGS = ''
...
#run(f'aplay {path}', sync, raise_error)
run(f'aplay {RUN_ARGS} {path}', sync, raise_error)

Now in my code I can
...
import chime
chime.RUN_ARGS = '--device sysdefault:CARD=PCH'

I'm not suggesting this is how it should be done, but rather the requested functionality. Thanks for the library!

Poetry's update recently changed both the lock file format and the build backend.

The lock file must be updated to support Poetry >= 1.1.0 and the build backend must be changed to "poetry.core.masonry.api".

The test workflow is failing after #6 because the workflow does not install the package. The workflow should install the package itself before running tests.

I have raised an Feature Request here with Conda/Anaconda to add this as an option on installs/creates etc. I haven't given it any though, but maybe there is a wrapper or call that can be made before a conda command that can make these alerts. Thought I'd raise it here to see if it was a valid idea!

Motivations - The number of times I have forgotten the -y argument and been pending on a large install is terrifying!

V cool package btw! Thx

Steps I took

• install in venv with pip3 install chime
• open python3 shell
• import chime and run chime.success()
• can't hear anything at all (no other audio is playing, audio is definitely working)

I can definitely help test some stuff if needed!

FYI 👍 https://calmcode.io/chime/introduction.html

Might be nice to add somewhere to the readme?

It would be cool to be able to specify a default theme somehow. Maybe in a config file like ~/.config/chime.conf?

[chime]
theme = zelda

Been thinking of a way to automatically trigger success/error sounds based on whether the previous command succeeded on the terminal.

One way to accomplish this would be an --exit-code (-e) argument to be used as such:

% ls; chime --exit-code=$?

$? in bash and zsh stores the exit code of the previous command. An exit-code argument would allow the user to input it into chime, triggering an error on a non-zero exit code, success otherwise.

To be honest I wish there was a more automated way to handle this, but this is the best I can come up with at the moment!

Cool library!

Would be great if we named the command so you could call the script from the command line using

% chime

instead of having to use

% python -m chime

This would also allow users to install the library using installers like pipx if they were interested in using it as a command-line tool.

The Material design resource page has some high quality notification sounds licensed under Creative Commons. It would make a great theme for some more typical notification sounds.