This isn't really an issue per say, but just want to get into contact with @kevinywlui .

First of all, great plugin! I love it! I use Arch Linux and like to add everything on my system through my package manager, so I wrote a PKGBUILD for Arch and put it on the AUR so anyone can use it (https://aur.archlinux.org/packages/zlong-alert-git). I'm listed as the maintainer there. If you want to take it over just let me know, it just tracks this git repo.

Feel free to close this issue whenever you want.

Hello! Nice repo and functionality!

I was wondering if there could be any support for temrminal sessions running on remote servers, and if it would be too complicated to make work.

I am willing to make a PR if it's feasible.

Any ideas?

# does work
for i in {0..15}; do sleep 1; echo "$i"; done

# does not work
    for i in {0..15}; do sleep 1; echo "$i"; done

Commands that start with a space get ignored because of how the cut command on line 43 works

switching to awk '{print $1}' should work but space is usually a way to ignore things so maybe adding an option could be cool.

echo 'command foo bar' | awk '{print $1}'
# -> command

echo '    for i in {0..15}; do sleep 1; echo "$i"; done' | awk '{print $1}'
# -> for

echo ' command  foo    bar thing' | awk '{print $1}'
# -> command

Hi, I've been using this plugin for a while now and find it very useful, however the notify_send package works only on Linux and not on MacOS.

I have made the required code changes on my machine and it has been working well for the past few months. So I would like to raise a PR to enable this plugin to officially support MacOS notifications.

I wanted to confirm that this is something the maintainer(s) of this project are interested in adding before going ahead with the PR. So please do let me know if I can start working on this.

Thanks a lot :)

Note: I would be adding a dependency on the alerter library to accomplish this

It would be nice to not pollute the global env so much. I think we should check the variables inside the functions they are used.

We should also clean up some of the small stuff like not quoting variables. I know its not always necessary in zsh but I think it makes some things confusing and has cased issues in the past.

The style should also be consistent. I'm fine with any style just as long as the plugin is consistent.

I haven't been a good steward of this repo (due to work getting busy) and should transfer it.

we just added a custom message variable for linux, it would be nice to test this on a mac though i dont have access to one.

Hi,

I notice an issue when using zlong_alert plugin with my existing zsh customizations.

Indeed, in my .zshrc I typically use this configuration :
setopt globsubst

Problem: this option break zlong_alert when using "eval" build-in command.

Without option globsubst :

% unsetopt globsubst

% eval $(echo date +"%D")
11/01/22

=> OK

With option globsubst :

% setopt globsubst

% eval $(echo date +"%D")
11/01/22
zlong_alert_post:3: missing end of string

% date +"%D"
11/01/22

=> eval command fails (regardless the duration of the command execution)

Maybe zlong_alert should use something like "emulate -L zsh" ?

According to man zshoptions :

       LOCAL_OPTIONS <K>
              If this option is set at the point of return from a shell  func‐
              tion, most options (including this one) which were in force upon
              entry to the function are restored; options  that  are  not  re‐
              stored  are PRIVILEGED and RESTRICTED.  Otherwise, only this op‐
              tion, and the LOCAL_LOOPS, XTRACE and  PRINT_EXIT_VALUE  options
              are  restored.   Hence  if  this  is explicitly unset by a shell
              function the other options in force at the point of return  will
              remain  so.   A shell function can also guarantee itself a known
              shell configuration with a formulation like  `emulate  -L  zsh';
              the -L activates LOCAL_OPTIONS.

Thanks

In oh-my-zsh, there's a global alias alias -g ....='../../..' which allows you to go back to the 3rd parent folder by typing ..... However, this command will make zlong_alert enter an infinite loop between these lines

given zlong_ignore_pfxs="sudo time" (the default) and cmd_head=.... isn't properly quoted for regex.

I'm not sure which way we should go to fix this. Maybe properly quote cmd_head? Or just use some heuristics, like don't check for prefixes if there isn't any whitespace in the command?