You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have a somewhat huge'ish amount of files ( ~140 files ), and when I run a bufdo in all of them, wakatime ( exactly python -W ignore /home/.../vim-wakatime/plugin/packages/wakatime/cli.py --entity ... ) spawns like 10+ processes, each consuming up to 5% of the cpu ( 50% in total ).
Is there a way to disable wakatime on bufdo's ? Is this expected behavior?
The text was updated successfully, but these errors were encountered:
If your bufdo command is writing to all open buffers, then WakaTime will think your coding in all those buffers. Maybe there's a way to detect bufdo usage and disable WakaTime for that command?
The way other editor plugins mitigate this is by buffering heartbeats in memory, then attaching them to one Python process as --extra-heartbeats every 10 seconds. That way all these Python processes would become one: sublime-wakatime/WakaTime.py#L529
Hello, I have a somewhat huge'ish amount of files ( ~140 files ), and when I run a bufdo in all of them, wakatime ( exactly python -W ignore /home/.../vim-wakatime/plugin/packages/wakatime/cli.py --entity ... ) spawns like 10+ processes, each consuming up to 5% of the cpu ( 50% in total ).
Is there a way to disable wakatime on bufdo's ? Is this expected behavior?
The text was updated successfully, but these errors were encountered: