-
Notifications
You must be signed in to change notification settings - Fork 12
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
let user define their process completed key word #22
Comments
@danie1Lin Thanks for your feature request. We are indeed missing the I think adding "$" | "#" | "%") Apart from that, I have no problem adding a variable to specify additional prompt separators (e.g. |
@danie1Lin A fix for the bug you were experiencing is shipped in v1.2.0. Can you verify whether it works on your system? I will keep this issue open so that we can discuss whether we want to also add a |
Thank you for fast-developing this feature, @rickstaa! |
@danie1Lin Thanks for your response and the use case. I added the I asked @ChanderG to review the pull request since it contains a significant change. If @ChanderG approves my pull request I will merge it under |
@danie1Lin Thanks a lot for testing my solution! Interesting, what is the literal version of your PS1 in that case? Is it Feel free to create a pull request on #24 if you think that is faster than explaining it here. The code can be debugged using breakpoints with the vscode bash extension using the following steps:
|
@danie1Lin I am currently not able to reproduce the problems you are experiencing. Did you see my previous questions? |
Hello guys, I was wondering why I'm using starship prompt that looks like below: As suggested in the above comment, I tried the following solution:
but it doesn't work. Any input is much appreciated. Thank you! |
Hey @kohane27. Could you maybe check if #24 solves your problem? I created that PR some time ago but since @danie1Lin didn't respond, did not merge it since I was uncertain if it worked. I'm happy to merge that pull request if it works for you 👍🏻. |
@danie1Lin and @kohane27 this feature was released under #24. You can now set the bash prefix of your choice using the following tmux config command: set -g @tnotify-prompt-suffixes '➜' |
Hello @rickstaa , Hope you're doing well. Apologies for not checking the fix from the earlier msg. I have just updated It's really handy to be notified about some long running processes. Thank you so much and have a good day! |
@cometta I do not know by head which symbols are used to create that prompt. Can you please give me the result of |
echo $PS1
|
Ah, the symbol you are looking for is the last character returned by the |
echo $(build_prompt)
yes i'm using https://ohmyz.sh/. as well |
Ah, I think this is the setup you're using:
The Main prompt
build_prompt() {
RETVAL=$?
prompt_status
prompt_context
prompt_dir
prompt_git
prompt_end
} Source: agnoster.zsh-theme This suffix is dynamically generated through the SEGMENT_SEPARATOR='⮀' Source: agnoster.zsh-theme For your scenario, you should set the following in your Tmux configuration: set -g @tnotify-prompt-suffixes '' If you also want to support bash, you can specify multiple suffixes: set -g @tnotify-prompt-suffixes ',$' |
it works. thank you |
Is your feature request related to a problem? Please describe.
At first, I found it did not work on my terminal. Then I looked into the script. I found we use # or $ to check the process if it is stopped.
here
But my command line is like 🤣
Describe the solution you'd like
If my understanding of the
notify.sh
is correct. We might let it be a customizable variable to capture the completed event.The text was updated successfully, but these errors were encountered: