New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added linux notification #2
Conversation
added "m" to string
Amazing!! Thank you so much. I shall test out later today. |
Hello, it turns out tmux has a nice command prompt. I added additional method to set the timer manually. Should probably add some validation there perhaps. Also, I wasn't sure if it should restart an existing timer. Please create an issue if you would like to discuss. |
Can confirm that it works on Mac perfectly. Regarding the custom pomodoro timer. I ❤️ the idea. Fully onboard. Only request...once you enter a value in the command prompt, can you trigger the countdown? I love that it stores the input for future pomodoros though. |
great, there are a few ways to go at this manual timer. It could stop any existing timer and start a new one. That's what I had done initially. But then I realized it might be more consistent to just use it for setting the timer and not interfere with anything else, and let the user start / stop it. At the moment, if a timer was already running, manually setting would make the existing timer look like it started from that timer. For instance: a. Start pomodoro with the hard coded timer, say 20 minutes. I think this is more consistent then resetting and restarting. But since we don't show the initial value, it could be also be confusing What do you think? Perhaps show the current value next to the count down? like 20m/20m 19/20m, 18/20m.. Another idea, to make the newly set timer value persist after a shutdown, we could read "try" to read @pomodoro_mins from a file during the first launch, it would be that file which the And finally, we could probably also prompt a task name, but then we would have to dive into multiline status bars, which might not look very uniform. |
I looked more into this, I think it's best to avoid the task name. A pomodoro timer is not a task manager, for that we have orgmode :) |
All really good points. My thoughts are that we run the risk of making this really complicated. Your initial idea of customising the timer is great and the API can be called out in the README to make it clear to all users. I'm keen to merge this into main, as-is. What are your thoughts? |
I think we should merge it as it is for now. I briefly looked into writing the new timer value to a file to make it permanent etc, but that turned out to be hackier than I thought. When you set the tmux variable through the command-prompt, and try to get it back right away doesn't appear to be working. It retrieves the previous value. Probably a |
This seems to have broken sound on macOS due to these lines. It checks if the sound is |
added "m" to string as well. Could you see if the os_check works for you on mac and merge if all is well?