From 202dc4ce820c5957a18e0d3d16503111a05bf8f9 Mon Sep 17 00:00:00 2001 From: tblancher Date: Wed, 11 Mar 2020 19:40:48 -0400 Subject: [PATCH] Fixed emphasis on 'Begin' and 'End' for KM section --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e6e92a9..95f749a 100644 --- a/README.md +++ b/README.md @@ -90,7 +90,7 @@ My Keyboard Maestro macros for timetracker make use of specific vim macros, and Several of the vim shortcuts I've programmed assist in managing the log text file. Invariably there will come a time where I forget to document a few tasks right away, so I piece together the logs from Slack and email, and edit the logs so it matches the format. One notable "normal" mode mapping is 'Y', which copies from the cursor position to the end of the line ('yanks' from the current position to the EOL, similar to 'C' or 'D' copying or deleting to the EOL). It is equivalent to the action 'y$', but is only one keystroke instead of two. The Keyboard Maestro macro for 'End' tasks uses this mapping heavily. ## Keyboard Maestro -Much of creating the log entries depends on specific Keyboard Maestro macros the author has set up. The file `timetracker.kmmacros` contains all of the macros used for this. The same text string trigger (Command + Shift + D, but you can assign it to any trigger) brings up a menu (known as a "conflict dialog" in KM), where I select '_B_egin' or '_E_nd'. The 'Begin' macro prints a log line using the current timestamp, like so: +Much of creating the log entries depends on specific Keyboard Maestro macros the author has set up. The file `timetracker.kmmacros` contains all of the macros used for this. The same text string trigger (Command + Shift + D, but you can assign it to any trigger) brings up a menu (known as a "conflict dialog" in KM), where I select '*B*egin' or '*E*nd'. The 'Begin' macro prints a log line using the current timestamp, like so: ``` 2020-03-11 19:14:42: Begin [CS Support] timetracker doc