I use this plugin for Git Windows and the change for path in commit #15 breaks that support!

if (( ! $+commands[wakatime] )); then  <--- This works
if ! wakatime_loc="$(type -p "$wakatime_bin")"; then <--- This does not work

Maybe some type of else check using the old logic might work.

It seems that the type -p command does not actually work on windows.
So if you get questions about this in the future that might be the issue.

wakatime-cli has functionality to automatically detect the Git branch that you're current working on, see here, here. However, the detection will only run if the heartbeat's entity is a file, see here.

For the ZSH plugin, I think it could be use useful to override that functionality by passing the current Git (or Mercurial?) branch in the current working directory (if existing) via --alternate-branch.

Brought up in the discussion at muety/wakapi#580 (reply in thread).

After following instructions from the official website I got the error plugin wakatime not found

https://wakatime.com/terminal#install-zsh

When installing Wakatime via homebrew, it is accessible as wakatime-cli not wakatime (at least lately). Is it an expected behaviour? Should I link the binary in order to satisfy this plugin?

This is the terminal message:

wakatime cli is not installed, run:
$ pip install wakatime
Or check that wakatime is in PATH

Time is not tracked for now.

Whether the new cli is the go one.

Hey guys,

When I install the plugin and set up ZSH, I get the following:

It works if I add this to my zsh config:

# Export Wakatime path
export ZSH_WAKATIME_BIN="/home/modem7/.wakatime/wakatime-cli"

this also works

# Export Wakatime path
export ZSH_WAKATIME_BIN="$HOME/.wakatime/wakatime-cli"

However this does not (still comes up with not installed):

# Export Wakatime path
export ZSH_WAKATIME_BIN="~/.wakatime/wakatime-cli"

Further testing: I've also added ls -la ~/.wakatime to my zsh config, and it properly outputs the .wakatime folder in my home directory.

Not quite sure where the issue is.

Would it be worthwhile changing the config from local wakatime_bin="${ZSH_WAKATIME_BIN:=~/.wakatime/wakatime-cli}" to local wakatime_bin="${ZSH_WAKATIME_BIN:=$HOME/.wakatime/wakatime-cli}"

At least for me last_command is always empty. It should be read here:
https://github.com/sobolevn/wakatime-zsh-plugin/blob/master/wakatime.plugin.zsh#L29

But this is empty for me. Might be my configuration, or other plugins I've loaded.
Googled for a quick bit, and switching to $history[$HISTCMD] solved it for me:
https://stackoverflow.com/a/25297732

Seems to be a good way to go about getting the last command, could provide a PR if wanted!

Original comment: https://www.reddit.com/r/zsh/comments/cajcni/wakatime_zsh_integration_track_how_much_time_you/etak2vd/

User @romkatv provided a wonderful review of the code: https://www.reddit.com/r/zsh/comments/cajcni/wakatime_zsh_integration_track_how_much_time_you/eta6ti1/

You want to hook preexec, not precmd.
Don't define globals with names bound to clash. E.g., PLUGIN_NAME.
It's better to use : {X:=Y} instead of X=${X:-Y}. However, in your code it's even better to not modify WAKATIME_TIMEOUT at all.
That $() in _wakatime_call is not doing what you think it does. Remove the parens.
Use &! instead of & to avoid polluting jobs.
Forks are slow. Avoid them. E.g., something like _should_work_online is definitely not worth the cost of a fork.
There is ${foo:t} to get the basename of a directory.
To check whether wakatime command exists, use if $(( $+commands[wakatime] )); ....
Don't trap signals. Traps are global, it's rude to hog them for yourself.
Prefix your functions with your project name such as _wakatime_. Try to limit the number of functions you define.

Would be really nice, if the plugin could read the projectmap defined in .wakatime.cfg.
Could fall back / use the existing behaviour, if that doesn't exist.

As all the other IDEs I'm using (vim, VS Code, PHPStorm) already respect that entry, which results in consistent projects in wakatime, it would be really nice to match that. Because git repositories don't necessarily map to projects in a 1:1 manner.

Would be open to trying my hands on a PR, just not sure how fast I'd be... as I'm not really knowledgeable in zsh scripting.

Hello,
after loading the plugin with

zplugin load sobolevn/wakatime-zsh-plugin

I'm seeing the following messages in the terminal:

usage: wakatime [-h] [--entity FILE] [--key KEY] [--write] [--plugin PLUGIN]
                [--time time] [--lineno LINENO] [--cursorpos CURSORPOS]
                [--entity-type ENTITY_TYPE] [--category CATEGORY]
                [--proxy PROXY] [--no-ssl-verify]
                [--ssl-certs-file SSL_CERTS_FILE] [--project PROJECT]
                [--alternate-project ALTERNATE_PROJECT] [--language LANGUAGE]
                [--local-file FILE] [--hostname HOSTNAME] [--disable-offline]
                [--hide-file-names] [--hide-project-names]
                [--hide-branch-names] [--exclude EXCLUDE]
                [--exclude-unknown-project] [--include INCLUDE]
                [--include-only-with-project-file] [--extra-heartbeats]
                [--log-file LOG_FILE] [--api-url API_URL] [--timeout TIMEOUT]
                [--sync-offline-activity SYNC_OFFLINE_ACTIVITY] [--today]
                [--config CONFIG] [--verbose] [--version]
wakatime: error: unrecognized arguments:

I didn't do any wakatime setup yet, i.e. there's no cfg file.

Sometimes I see that calls take too long. I decreases my UX.
So, maybe it is a good idea to make these call async?

Something like: https://github.com/mafredri/zsh-async