2015-12-02 14:23:39 +00:00
|
|
|
#+TITLE: Wakatime layer
|
2015-07-24 01:38:52 +00:00
|
|
|
|
|
|
|
|
[[file:img/wakatime.png]]
|
|
|
|
|
|
2016-03-31 02:59:55 +00:00
|
|
|
* Table of Contents :TOC_4_gh:noexport:
|
2017-05-22 14:16:12 +00:00
|
|
|
- [[#description][Description]]
|
2017-12-21 17:27:23 +00:00
|
|
|
- [[#features][Features:]]
|
2017-05-22 14:16:12 +00:00
|
|
|
- [[#install][Install]]
|
|
|
|
|
- [[#wakatime-program][Wakatime Program]]
|
|
|
|
|
- [[#layer][Layer]]
|
|
|
|
|
- [[#api-keys][API Keys]]
|
|
|
|
|
- [[#note-to-venv-workon-users][Note to =venv-workon= users:]]
|
2015-07-24 01:38:52 +00:00
|
|
|
|
|
|
|
|
* Description
|
|
|
|
|
This layer adds support for Wakatime.
|
|
|
|
|
|
|
|
|
|
WakaTime was built to solve time tracking for programmers.
|
|
|
|
|
Since we work inside a text editor, why should we have to start and stop a
|
|
|
|
|
timer? WakaTime uses open-source text editor plugins to automatically track the
|
|
|
|
|
time you spend programming so you never have to manually track it again!
|
|
|
|
|
|
|
|
|
|
P.S. wakati means time in Swahili
|
|
|
|
|
|
2017-12-21 17:27:23 +00:00
|
|
|
** Features:
|
|
|
|
|
- Integration with Wakatime cloud based time tracking service
|
|
|
|
|
|
2015-07-24 01:38:52 +00:00
|
|
|
* Install
|
|
|
|
|
** Wakatime Program
|
|
|
|
|
You can follow wakatime installation instructions here
|
|
|
|
|
https://github.com/wakatime/wakatime-mode.
|
|
|
|
|
|
|
|
|
|
In short it's just:
|
|
|
|
|
#+BEGIN_SRC sh
|
|
|
|
|
pip install wakatime
|
|
|
|
|
#+END_SRC
|
|
|
|
|
|
|
|
|
|
And for some linux users
|
|
|
|
|
#+BEGIN_SRC sh
|
|
|
|
|
sudo pip install wakatime
|
|
|
|
|
#+END_SRC
|
|
|
|
|
|
|
|
|
|
** Layer
|
2016-01-06 05:21:55 +00:00
|
|
|
To use this configuration layer, add it to your =~/.spacemacs=. You will need to
|
|
|
|
|
add =wakatime= to the existing =dotspacemacs-configuration-layers= list in this
|
|
|
|
|
file.
|
2015-07-24 01:38:52 +00:00
|
|
|
|
2016-01-06 05:21:55 +00:00
|
|
|
Example:
|
2015-07-24 01:38:52 +00:00
|
|
|
#+BEGIN_SRC emacs-lisp
|
2015-10-13 13:57:59 +00:00
|
|
|
(setq-default dotspacemacs-configuration-layers
|
2016-01-06 05:21:55 +00:00
|
|
|
'(
|
|
|
|
|
;; ...
|
|
|
|
|
(wakatime :variables
|
|
|
|
|
wakatime-api-key "your-api-key"
|
|
|
|
|
;; use the actual wakatime path
|
|
|
|
|
wakatime-cli-path "/usr/bin/wakatime")
|
|
|
|
|
;; ...
|
|
|
|
|
))
|
2015-07-24 01:38:52 +00:00
|
|
|
#+END_SRC
|
|
|
|
|
|
|
|
|
|
** API Keys
|
|
|
|
|
After this go to your wakatime account and have your API key handy
|
|
|
|
|
https://wakatime.com/settings/account?apikey=true .
|
|
|
|
|
|
|
|
|
|
Restart emacs and it will prompt you for the location of the wakatime installer
|
|
|
|
|
(just put in whatever =which wakatime= gives you in the terminal e.g.
|
|
|
|
|
=/usr/bin/wakatime= for example) and that's it.
|
|
|
|
|
|
|
|
|
|
*** Note to =venv-workon= users:
|
|
|
|
|
Right now wakatime uses =python= as python bin executable, so if you use
|
|
|
|
|
=venv-workon= because you have python projects which need to have a virtual
|
|
|
|
|
env., then wakatime, which is installed system-wide will have trouble locating
|
|
|
|
|
wakatime files, so it's best to define by yourself the python path where
|
|
|
|
|
wakatime can always find it's stuff, via this variable:
|
|
|
|
|
|
|
|
|
|
#+BEGIN_SRC emacs-lisp
|
|
|
|
|
(setq wakatime-python-bin "/path/to/python")
|
|
|
|
|
#+END_SRC
|
