Final commit before re-publication

2025-08-23 09:34:15 -04:00
parent 58830d9be8
commit d0fcd32c91
6 changed files with 401 additions and 40 deletions
--- a/.gitignore
+++ b/.gitignore
@@ -6,9 +6,10 @@
 !chug.sh
 !clean_timetracker_staging.zsh
 !do_process.sh
-images
+!images
 !INSTALL_Linux.md
 !INSTALL_macOS.md
 !LICENSE
 !month-pack.sh
 !README.md
 !rust
@@ -17,5 +18,6 @@ images
 !timetracker.py
 !timetracker-sections.pl
 !timetracker.vim
 !.vimrc
 !vim
 !year-pack.sh
--- a/.vimrc
+++ b/.vimrc
@@ -0,0 +1,108 @@
 set nomodeline
 set t_Co=256
 "set t_Co=16
 set t_ut=
 set ai
 set background=dark
 "set background=light
 "set textwidth=80
 set hlsearch
 "color asu1dark
 "set t_ut=
 let g:solarized_italic=0
 "let g:solarized_bold=0
 "let g:solarized_underline=0
 "colorscheme sorcerer
 let g:csv_delim=','
 " Pathogen
 filetype off " Pathogen needs to run before plugin indent on
 "execute pathogen#infect()
 "call pathogen#runtime_append_all_bundles()
 "call pathogen#helptags() " generate help tags for everything in 'runtimepath'
 filetype plugin indent on
 filetype plugin on 
 "colorscheme gruvbox
 syntax on
 set tabstop=4
 set softtabstop=4
 set shiftwidth=4
 set expandtab
 nnoremap <F2> :GundoToggle<CR>                                               
 nnoremap <C-j>	<C-w>w
 "imap   <End>
 "imap   <Home>
 "nnoremap   $
 "nnoremap   <bar>
 nmap Y y$
 nmap C c$
 "nnoremap V <C-v>
 "inoremap jj <Esc>
 "inoremap kk <Esc>
 "inoremap hh <Esc>
 "inoremap lll <Esc>
 "inoremap bbb <Esc>
 "inoremap eeee <Esc>
 "inoremap ww <Esc>
 "inoremap yy <Esc>yy
 "inoremap ddd <Esc>dd
 "inoremap dG <Esc>dG
 "inoremap :w <Esc>:w
 "inoremap :wq <Esc>:wq
 "inoremap :q <Esc>:q
 "inoremap :q! <Esc>:q!
 "nnoremap <S-Tab> <<
 "inoremap <S-Tab> <C-d>
 " Force me to stop using arrow keys
 "inoremap <Left> <Nop>
 "nnoremap <Left> <Nop>
 "inoremap <Right> <Nop>
 "nnoremap <Right> <Nop>
 "inoremap <Up> <Nop>
 "nnoremap <Up> <Nop>
 "inoremap <Down> <Nop>
 "nnoremap <Down> <Nop>
 " Fix Home/End/Delete
 set backspace=indent,eol,start
 "fixdel
 " Idle timeout, exit insert mode after thirty seconds:
 "au CursorHoldI * stopinsert
 "set updatetime=30000
 "if $TMUX == ''
 "  set clipboard+=unnamed
 "endif
 set clipboard+=unnamed
 set laststatus=2
 set statusline=[%n]\ %<%F\ \ \ [%M%R%H%W%Y][%{&ff}]\ \ %=\ line:%l/%L\ col:%c\ \ \ %p%%\ \ \ @%{strftime(\"%H:%M:%S\")}
 if $VIM_CRONTAB == "true"
    set nobackup
    set nowritebackup
 endif
 "set spell spelllang=en
 " Change cursor shape between insert and normal mode in iTerm2.app
 if $TERM_PROGRAM =~ "iTerm.app"
    if exists('$TMUX')
        let &t_SI = "\<Esc>Ptmux;\<Esc>\<Esc>]50;CursorShape=1\x7\<Esc>\\" " Vertical bar in insert mode
        let &t_EI = "\<Esc>Ptmux;\<Esc>\<Esc>]50;CursorShape=0\x7\<Esc>\\" " Block in normal mode
        let &t_SR = "\<Esc>Ptmux;\<Esc>\<Esc>]50;CursorShape=2\x7\<Esc>\\" " Block in normal mode
    else
        let &t_SI = "\<Esc>]50;CursorShape=1\x7" " Vertical bar in insert mode
        let &t_EI = "\<Esc>]50;CursorShape=0\x7" " Block in normal mode
        let &t_SR = "\<Esc>]50;CursorShape=2\x7" " Block in normal mode
    endif
 endif
 if has("autocmd")
      au BufReadPost * if line("'\"") > 0 && line("'\"") <= line("$") | exe "normal! g`\"" | endif
 endif
 autocmd BufRead,BufNewFile ~/pindrop/meetings/cs_support_weekly/* source ~/.muttvimrc
 autocmd BufRead,BufNewFile ~/pindrop/meetings/cs_support_proactive_monitoring/* source ~/.muttvimrc
 autocmd BufRead,BufNewFile ~/meetings/* source ~/.muttvimrc
--- a/INSTALL_Linux.md
+++ b/INSTALL_Linux.md
@@ -5,7 +5,7 @@ Use `git clone` to create a local copy of the timetracker repository on your loc
 If you'd prefer to use the Rust programs (which is highly recommended, if only for execution speed), you will need to compile the Rust programs with `cargo` (the Rust language package manager).  Do the following:
 1.  Install Rust language using your chosen distribution's package manager.  For Arch Linux:
    ```
-    pacmak -Syu rust
+    pacman -Syu rust
    ```
 1.  Navigate to the `timetracker/rust/timetracking` directory in the cloned `timetracker` source directory
 1.  Execute the following command:
@@ -19,5 +19,5 @@ If you'd prefer to use the Rust programs (which is highly recommended, if only f
      cargo run -- <input arguments>
      ```
 ## Pro Tips (TODO)
- X11/X.org macros
+- X11/X.org macros (autokey)
- Wayland/Hyprland macros
+- Wayland/Hyprland macros (hyprctl dispatch/espanso)
--- a/INSTALL_macOS.md
+++ b/INSTALL_macOS.md
@@ -33,12 +33,15 @@ for use.
      change directory to whichever executable you're working on (`chug`,
      `doprocess`, `timetracker`, or the library package `timelogging`), you
      will likely want to run the debug version directly, like so: ``` cargo
-      run -- <input arguments> ``` ## Pro Tips There are some things that you
+      run -- <input arguments> ``` 
-      need to do in order to use timetracker like a pro.  These instructions
+
-      assume you're using the vim or gvim (GUI) editor.  There are likely
+## Pro Tips 
-      similar macros you can enable for editors such as Visual Studio Code,
+
-      Sublime, but you'll have to review the documentation for those editors to
+There are some things that you need to do in order to use timetracker like a
-      be able to reproduce the ideas there.  
+pro.  These instructions assume you're using the vim or gvim (GUI) editor.
 There are likely similar macros you can enable for editors such as Visual
 Studio Code, Sublime, etc., but you'll have to review the documentation for those
 editors to be able to reproduce the ideas there.  
 Here are the basics for using the `timetracker` (print summary of a timetracker
 log file), `do_process` (print the summary of a log file broken down by
@@ -85,7 +88,10 @@ details:
    can begin using them.  In your favorite terminal emulator (e.g. Alacritty,
    iTerm2, Kitty, or Terminal.app), open vim on today's log file: 
-    ```sh cd ~/timetracker vim 2020-04-07.log ```
+    ```sh 
    cd ~/timetracker
    vim 2020-04-07.log
    ```
    Or, if you prefer, use gvim or Mac vim GUI programs. 
--- a/232
+++ b/232
@@ -0,0 +1,232 @@
 GNU GENERAL PUBLIC LICENSE
 Version 3, 29 June 2007
 Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
 Preamble
 The GNU General Public License is a free, copyleft license for software and other kinds of works.
 The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
 When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
 To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
 For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
 Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
 For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
 Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
 Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
 The precise terms and conditions for copying, distribution and modification follow.
 TERMS AND CONDITIONS
 0. Definitions.
 “This License” refers to version 3 of the GNU General Public License.
 “Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
 “The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
 To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
 A “covered work” means either the unmodified Program or a work based on the Program.
 To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
 To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
 An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
 1. Source Code.
 The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
 A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
 The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
 The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
 The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
 The Corresponding Source for a work in source code form is that same work.
 2. Basic Permissions.
 All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
 You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
 Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
 No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
 When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
 4. Conveying Verbatim Copies.
 You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
 You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
 5. Conveying Modified Source Versions.
 You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
     a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
     b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
     c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
     d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
 A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
 6. Conveying Non-Source Forms.
 You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
     a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
     b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
     c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
     d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
     e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
 A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
 A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
 “Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
 If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
 The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
 Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
 7. Additional Terms.
 “Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
 When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
 Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
     a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
     b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
     c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
     d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
     e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
     f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
 All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
 If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
 Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
 8. Termination.
 You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
 However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
 Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
 Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
 9. Acceptance Not Required for Having Copies.
 You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
 10. Automatic Licensing of Downstream Recipients.
 Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
 An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
 You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
 11. Patents.
 A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
 A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
 Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
 In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
 If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
 If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
 A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
 Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
 12. No Surrender of Others' Freedom.
 If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
 13. Use with the GNU Affero General Public License.
 Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
 14. Revised Versions of this License.
 The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
 Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
 If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
 Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
 15. Disclaimer of Warranty.
 THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
 16. Limitation of Liability.
 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
 17. Interpretation of Sections 15 and 16.
 If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
 END OF TERMS AND CONDITIONS
 How to Apply These Terms to Your New Programs
 If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
 To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
     <one line to give the program's name and a brief idea of what it does.>
     Copyright (C) <year>  <name of author>
     This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.
     You should have received a copy of the GNU General Public License along with this program.  If not, see <https://www.gnu.org/licenses/>.
 Also add information on how to contact you by electronic and paper mail.
 If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
     <program>  Copyright (C) <year>  <name of author>
     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
     This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
 The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
 You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>.
 The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/philosophy/why-not-lgpl.html>.
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
 # timetracker
-tblancher's CLI-based time tracking system (see demo videos of the [timetracker setup](https://pindrop.zoom.us/rec/share/wvN6FoPfyEhJfo3x12qFVKofHL30X6a81Sce__IJmEp90tBtwdKHn7JnxZMQfz69), [macro setup](https://pindrop.zoom.us/rec/share/w-lYBpf2q0hLYpHR-n7bY6gwMr_Caaa81ClK__YJmR2E6NY1ybj-wurKfyog0FpO), and [Clarizen process](https://pindrop.zoom.us/rec/share/yuF4C7_7rFlJAYnAq2TwarETAorMeaa8gXQdqfUPnRsgkXJf9_ByKUpI8hnGW1Jp))
+tblancher's CLI-based time tracking system 
 ## INSTALLATION
 See [INSTALL_Linux.md](INSTALL_Linux.md) or [INSTALL_macOS.md](INSTALL_macOS.md) in this repository.
@@ -48,18 +48,19 @@ think they're different tasks).
 Certain strings have special meaning to timetracker.  The category name in
 square brackets specifies that the task is related to a specific customer, or
-should be tracked on a certain item in Clarizen, to make transferring to
+should be tracked on a certain item in the official timelog, to make
-Clarizen more straightforward.  These can be any string, even with spaces, but
+transferring to the official timesheet more straightforward.  These can be any string, even
-beware of using shell special characters, or special regular expression
+with spaces, but beware of using shell special characters, or special regular
-characters.  The names can be anything, so things like `[Project Phoenix]`, `[Java training]`,
+expression characters.  The names can be anything, so things like `[Project
-`[Commute]`, or `[Internal]` are perfectly valid.  For the author's most
+Phoenix]`, `[Java training]`, `[Commute]`, or `[Internal]` are perfectly valid.
-common categories, macros are set up with text string triggers in Keyboard
+For the author's most common categories, macros are set up with text string
-Maestro (more on that below).  If you decide to use `timetracker.py` (the
+triggers in Keyboard Maestro (more on that below).  If you decide to use
-Python 3 script), the category (in square-brackets) is optional, but won't have
+`timetracker.py` (the Python 3 script), the category (in square-brackets) is
-a separate section in `do_process.sh` (though it will reflect in the grand
+optional, but won't have a separate section in `do_process.sh` (though it will
-total at the end).  If you decide to use the Rust programs, the category is
+reflect in the grand total at the end).  If you decide to use the Rust
-**required**, or else the Rust programs will panic and error out.  It is highly
+programs, the category is **required**, or else the Rust programs will panic
-recommended to use the Rust programs, for speed if nothing else.
+and error out.  It is highly recommended to use the Rust programs, for speed if
 nothing else.
 Note that the aggregate programs (`do_process.sh`, `doprocess` [Rust],
 `chug.sh`, `chug` [Rust]) expect the log file to be named by the ISO-8601 date
@@ -86,7 +87,7 @@ amount of time I was spending during my day.
 ## timetracker in Rust
-Again, see the [INSTALL.md](https://github.atl.pdrop.net/tblancher/timetracker/blob/master/INSTALL.md) guide in this repository for instructions on building the Rust programs.  It is highly recommended to use the Rust programs instead of the older Python and Bash scripts below, if only because the Rust programs are much, much faster to execute than the older scripts.  The usage is straightforward:
+Again, see the [INSTALL_Linux.md](https:/git.eldon.me/trey/timetracker/primary/INSTALL_Linux.md) or [INSTALL_macOS.md](https:/git.eldon.me/trey/timetracker/primary/INSTALL_macOS.md) guides in this repository for instructions on building the Rust programs.  It is highly recommended to use the Rust programs instead of the older Python and Bash scripts below, if only because the Rust programs are much, much faster to execute than the older scripts.  The usage is straightforward:
 ### timetracker usage
 Pass the log name as the only argument to `timetracker`.  Alternatively, you can execute a command pipeline that generates valid log output in the format above, piping it into timetracker:
@@ -112,7 +113,7 @@ Grand total: 7.16
 This is the only Rust program that does not necessarily assume the log will be named in the ISO-8601 date format with `.log` filename extension (e.g. `2022-11-30.log`, `2022-12-19.log`, etc.).  You can run this periodically throughout the day as you build the log file to see how much time you've put in thus far.  
 ### doprocess usage
-`doprocess` relies on the same internal Rust functions as `timetracker`, with the added output feature of separating the various categories into their own sections, for even easier transfer to Clarizen.  With the new Clarizen categories, this makes entry into Clarizen take five minutes or less.  You may want to sort your categories in Clarizen, to match the sort out of `doprocess`.  Each section has its own total, with a running subtotal you can use to confirm you haven't missed anything as you transfer them to Clarizen.  Its output looks like this:
+`doprocess` relies on the same internal Rust functions as `timetracker`, with the added output feature of separating the various categories into their own sections, for even easier transfer to the official timesheet.  Each category will hav its own subtotal, with a running subtotal you can use to confirm you haven't missed anything as you transfer the entries to the official timesheet.  Its output looks like this:
 ```
 [Cloud] Customer 1 PDROP-0000000 case-related task 1                          0.75hrs
 [Cloud] Customer 1 task 1                                                     0.08hrs
@@ -141,10 +142,10 @@ Subtotal:           7.16hrs
 Grand total: 7.16
 ```
-For everything but the [Internal] category, you should be able to copy the entire section with Section total to a single line item in Clarizen.  The Section total and Subtotal for the [Internal] category can be input as separate line items for each entry, and these totals help ensure you haven't missed one or input its duration improperly.
+For everything but the [Internal] category, you should be able to copy the entire section with Section total to a single line item in the official timesheet.  The Section total and Subtotal for the [Internal] category can be input as separate line items for each entry, and these totals help ensure you haven't missed one or input its duration improperly.
 ### chug usage
-`chug` does not take a filename, or a log in the above format.  Instead, it looks at the current week, and calculates the grand total for each day.  If any day is missing, because the log file doesn't exist, it will print 0.00 for that day, like so:
+`chug` does not take a filename, or a log in the above format.  Instead, it looks at the current week starting on Monday, and calculates the grand total for each day by examining each log file (this is why it's stongly recommended to have one log per day, with the date in the filename).  If any day is missing, because the log file doesn't exist, it will print 0.00 for that day, like so:
 ```
 2022-12-19.log
@@ -170,7 +171,7 @@ For everything but the [Internal] category, you should be able to copy the entir
 Grand total: 8.38
 ```
-You can use this to review Clarizen, and make sure all time is input correctly.  If you'd like to look at a previous week, you can pass the optional argument `1` or `+1`, `n` or `+n` where `n` is an unsigned integer for even further back.  If you will be out of office on extended leave for the next week, and wish to run `chug` for it, pass a negative integer (e.g. `-1`, or `-n`).  The formula for the week `chug` will look at is as follows:
+You can use this to review the official timesheet, and make sure all time is input correctly.  If you'd like to look at a previous week, you can pass the optional argument `1` or `+1`, `n` or `+n` where `n` is an unsigned integer for even further back.  If you will be out of office on extended leave for the next week, and wish to run `chug` for it, pass a negative integer (e.g. `-1`, or `-n`).  The formula for the week `chug` will look at is as follows:
 ```
 <last Monday> - <week offset>
@@ -189,12 +190,24 @@ Similarly, if you have too many End timestamps, you'll get an error that looks l
 thread 'main' panicked at 'ERROR:  Missing a Begin', timelogging/src/lib.rs:101:21
 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ```
-For correct operation, there should be an equal number of Begin and End timestamps.  If you're in the middle of a task, the last End is optional, if it's the first entry of that task it will be the minimum duration (0.08 hours).
+For correct operation, there should be an equal number of Begin and End timestamps.  If you're in the middle of a task, the last End is optional;  if it's the first entry of that task it will be the minimum duration (0.08 hours).
 # Older Python and Bash scripts, for comparison
 ## timetracker.py usage
 The timetracker.py script is the basis, it tallies the time for each task and then outputs a report on how much each task takes to complete.  It takes as its argument one or more text files, the log files in the format above.  It should only report one line item per task, regardless of how many times it appears in the log.  Each task should have a category/tag in square brackets, the behavior of `do_process.sh` (see below) is now undefined if the tag is left out.
-Note that the time gets rounded to the nearest quarter hour.  If it would round to zero hours (0.00hrs), the script replaces it 0.08hrs, which corresponds to 288 seconds.  If you don't want a task to be set to 0.08hrs, simply leave it out of the log.  Prior to the merge of nearest-quarter-hour, everything was rounded UP to the nearest quarter hour.  That meant that if a task took 30 minutes and one second, it would be rounded UP to 0.75hrs (45 minutes).  On longer days this had the effect of inflating the daily total, such that 10 hours of actual work was being inflated to 12 or even 13 hours on some occasions.  Now that it rounds up or down to the nearest quarter hour, timetracker.py is much more accurate.  There still is a bit of inflation for the short tasks (anything taking less than 288 seconds), but it shouldn't be as bad as adding an extra 15 minutes to tasks that are close to quarter hour boundaries.
+Note that the time gets rounded to the nearest quarter hour.  If it would round
 to zero hours (0.00hrs), the script replaces it with 0.08hrs, which corresponds
 to 288 seconds.  If you don't want a task to be set to 0.08hrs, simply leave it
 out of the log.  Prior to the merge of nearest-quarter-hour, everything was
 rounded UP to the nearest quarter hour.  That meant that if a task took 30
 minutes and one second, it would be rounded UP to 0.75hrs (45 minutes).  On
 longer days this had the effect of inflating the daily total, such that 10
 hours of actual work was being inflated to 12 or even 13 hours on some
 occasions.  Now that it rounds up or down to the nearest quarter hour,
 timetracker.py is much more accurate.  There still is a bit of inflation for
 the short tasks (anything taking less than 288 seconds), but it shouldn't be as
 bad as adding an extra 15 minutes to tasks that are close to quarter hour
 boundaries.
 The output looks like this:
@@ -216,7 +229,7 @@ Section total:          8.41hrs
 You may have noticed, the output of timetracker.py is in alphabetical order by category, then by task.  This follows for `./do_process.sh` and `./chug.sh` below.  
 ## `do_process.sh`
-This script filters the output of timetracker.py, giving each category (in square brackets) its own section, with its own tallies.  The header is the list of categories and the log file basename (below this is `example.log`, but would normally be a date such as `2017-12-08.log`).  After the header, each line of output and sections are designed to be directly transferred to Clarizen manually, and the tally used to verify the daily and weekly totals in Clarizen.  It calculates the time total for each organization/category.  It also prints the subtotal thus far, to be sure no items are missed when adding them to Clarizen.  At the end it prints a grand total for the day, which should be used along with the subtotals to cross-verify in Clarizen.
+This script filters the output of timetracker.py, giving each category (in square brackets) its own section, with its own subtallies.  The header is the list of categories and the log file basename (below this is `example.log`, but would normally be a date such as `2017-12-08.log`).  After the header, each line of output and sections are designed to be directly transferred to the official timesheet manually, and the tally used to verify the daily and weekly totals in the official timesheet.  It calculates the time total for each organization/category.  It also prints the subtotal thus far, to be sure no items are missed when adding them to the official timesheet.  At the end it prints a grand total for the day, which should be used along with the subtotals to cross-verify in the official timesheet.
 ```
 [Internal]
@@ -265,14 +278,14 @@ Grand total:          8.41hrs
 It takes as its argument a filename with the current date log (`date +%F` format, such as `./do_process.sh 2020-03-12.log`), or it assumes the current date log file.  Also, arbitrary filenames can be passed, so `example.log` becomes `./do_process.sh example.log`.
-Projects in Clarizen are listed alphabetically, so to transfer data from the `./do_process.sh` output you simply copy the data lines from the ouput, and paste it into the notes section of the Clarizen entry.  Enter the duration of the task at the top of the Clarizen entry, and select the category and subcategory of the entry.
+Projects in the official timesheet are listed alphabetically, so to transfer data from the `./do_process.sh` output you simply copy the data lines from the ouput, and paste it into the notes section of the official timesheet entry.  Enter the duration of the task at the top of the official timesheet entry, and select the category and subcategory of the entry.
 ## `chug.sh`
-This script is designed to be run on Mondays, after the previous week of log files have been generated and closed out. The standard Monday usage takes no arguments, it expects all log files to be processed to be in the current directory.  It runs `do_process.sh` once for each day of the previous week, cleanly skipping any log files which do not exist.  It pauses after each day report is output, allowing the user to transfer the times manually to Clarizen.  
+This script is designed to be run on Mondays, after the previous week of log files have been generated and closed out. The standard Monday usage takes no arguments, it expects all log files to be processed to be in the current directory.  It runs `do_process.sh` once for each day of the previous week, cleanly skipping any log files which do not exist.  It pauses after each day report is output, allowing the user to transfer the times manually to the official timesheet.  
 `./chug.sh` takes a single optional argument, a week offset (in case `./chug.sh` is executed for log files further back than last week).  This uses the GNU date functionality of calculating "last Monday."  On Monday this will be "today - 7 days", but on the following Tuesday this will evaluate to "yesterday".  If Monday is a holiday and you're entering your timesheets on Tuesday you can enter `./chug.sh 1` and it should do the right thing.  If it's the first Monday of the month and you need to process the previous four weeks of logs, use `./chug.sh 4`.  The output of `./do_process.sh` prints the date that is being processed at the top, if your incantation of `./chug.sh` is wrong, you can quit and adjust accordingly.  `./chug.sh` with no arguments is equivalent to `./chug.sh 0`.
-The output is the output of `./do_process.sh` piped to `less` for each day, pausing so the user can go through that day's output and transfer the items to Clarizen.  If no time was logged for a given day (the file does not exist), `./chug.sh` prints the missing date, but otherwise silently skips it.  All seven days of the week are processed, Monday through Sunday.
+The output is the output of `./do_process.sh` piped to `less` for each day, pausing so the user can go through that day's output and transfer the items to the official timesheet.  If no time was logged for a given day (the file does not exist), `./chug.sh` prints the missing date, but otherwise silently skips it.  All seven days of the week are processed, Monday through Sunday.
 If you're only interested in the weekly summary (and don't want the output of `./do_process.sh <date>.log | less`), you can pass the `-i` option to `./chug.sh`, like so:  `./chug -i`, or if you need a prior week, e.g. `./chug -i 2`.  The output will look similar to the following:  
@@ -302,16 +315,16 @@ Weekly Total:  48.79
 ```
 ## month-pack.sh
-timetracker.py and the related `do_process.sh` and `chug.sh` scripts are designed to have each day with its own YYYY-MM-DD.log file in the current, timetracker directory.  Over time, the log files in this directory can become quite numerous and unwieldy.  To help combat this, `month-pack.sh` takes all the log files from the previous month, adds them to a compressed tarball, and deletes them from the directory.  It is designed to be run once all of the log files for the previous month have been processed into Clarizen.
+timetracker.py and the related `do_process.sh` and `chug.sh` scripts are designed to have each day with its own YYYY-MM-DD.log file in the current, timetracker directory.  Over time, the log files in this directory can become quite numerous and unwieldy.  To help combat this, `month-pack.sh` takes all the log files from the previous month, adds them to a compressed tarball, and deletes them from the directory.  It is designed to be run once all of the log files for the previous month have been processed into the official timesheet.
 ## year-pack.sh
 In the same vein as month-pack.sh, year-pack.sh tars up all the monthly tarballs (named YYYY-MM.tar.xz), and puts them into a single YYYY.tar file.  It is designed to be run in January when all of the previous December log files have been processed.  All of the YYYY-MM.tar.xz files will be deleted once the YYYY.tar file is created.
 # CAVEATS
 ## Tallies
-Since I (the author, Trey Blancher) have been using this system to keep track of time, I've noticed that sometimes either Clarizen or these scripts get slightly off.  Usually it's no more than 0.25 hours off in the tallies, but it gets time consuming trying to track down where the tally went wrong.  If I do find the culprit, it's usually because I've entered the wrong time for a specific task in Clarizen (i.e., entering '0.08' instead of '0.25' for some tasks), or I've entered the time in the wrong cell.
+Since I (the author, Trey Blancher) have been using this system to keep track of time, I've noticed that sometimes either the official timesheet or these scripts get slightly off.  Usually it's no more than 0.25 hours off in the tallies, but it gets time consuming trying to track down where the tally went wrong.  If I do find the culprit, it's usually because I've entered the wrong time for a specific task in the official timesheet (i.e., entering '0.08' instead of '0.25' for some tasks), or I've entered the time in the wrong cell.
 ### 2020-09-16 UPDATE
-As of the institution of the running subtotals, the tallies being off in Clarizen is a *MUCH* less frequent problem.  Usually if Clarizen is off it's because I missed an entry, or Clarizen didn't absorb an entry properly (that happens from time to time).
+As of the institution of the running subtotals, the tallies being off in the official timesheet is a *MUCH* less frequent problem.  Usually if the official timesheet is off it's because I missed an entry, or the official timesheet didn't absorb an entry properly (that happens from time to time).
 ## vim
 The vim-specific files in this repository are tailored for my tastes.  One big item of note, I've disabled vim cursor navigation with the arrow keys (Up, Down, Left, Right), to force me to get into the habit of using h, j, k, l for cursor navigation, and only navigate in normal mode (not insert mode).  You will probably want to delete the following lines from .vimrc if you're not interested in the true Vim way®:
@@ -345,6 +358,6 @@ The 'End' macro copies the category and task name from the previous 'Begin' macr
 2020-03-11 19:30:36:  End   [Internal] timetracker doc
 2020-03-11 19:30:36:  Begin 
 ```
-I also have Keyboard Maestro text string triggers for common categories, to minimize typing.  For instance, the text string triggers `[css` becomes `[Internal] `, `[pro` becomes `[Internal] `, `[mm` or `[MM` becomes `[Mass Mutual] `, `[vzw` becomes `[Verizon Wireless] `, `[pin` becomes `[Company] ` (to match the Pindrop related items in Clarizen), etc.  These are included in `timetracker.kmmacros` for your convenience.
+I also have Keyboard Maestro text string triggers for common categories, to minimize typing.  For instance, the text string triggers `[css` becomes `[Internal] `, `[pro` becomes `[Internal] `, `[mm` or `[MM` becomes `[Mortimer Mouse] `, `[vzw` becomes `[Vizier Works] `, `[pin` becomes `[Company] ` (to match the Pindrop related items in the official timesheet), etc.  These are included in `timetracker.kmmacros` for your convenience.
-See [INSTALL.md](https://github.atl.pdrop.net/tblancher/timetracker/blob/master/INSTALL.md) in this repository for a detailed explanation of how to use the `timetracker.kmmacros` and set up the vim macros.
+See [INSTALL_macOS.md](https://git.eldon.me/trey/timetracker/blob/primary/INSTALL_macOS.md) in this repository for a detailed explanation of how to use the `timetracker.kmmacros` and set up the vim macros.