dsu 2.1.1 → 2.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 53ef02b21bb75d6e3e4bed1f8e9db48e7dd62e431eae71421f33ba6dbd5d780c
-  data.tar.gz: 87430adbb8f5043623ae38050e13be1167418beabe5cd1b18e03e234f4a29fa9
+  metadata.gz: f56239cec153192ff0f815e124e8001ab7676c418f334ff328512c6cfc11eeb4
+  data.tar.gz: d0072d4760663b70d32fa5695c6dbae27db960b95017a0a49598ef53a0bba588
 SHA512:
-  metadata.gz: 9d28ad896fb311662825c295431607b3633de799a206949683518c5230232533d44f3151c411c25dc7d18396adfe200e2580239d26fdd32015e40e6e601c3608
-  data.tar.gz: e3e411cda8d2eeba5a5cb8d7dc86efb3f552b83d25c4518ea4db2024cee5ffead9aacdb870193a14153794a35ed76216d00fdb00d2094e0f008542da4e6756c0
+  metadata.gz: 8e60d02338b12cd52c7f2a0b4f8f5f633879c6c3e7614b8fd1563d03348e778e9cb6f83a674e0be9bf53b5cac878e058d045834ce7c0f615e12129830fc2ca5b
+  data.tar.gz: d6807da2999520c94dbe54b5439b52a386701a20e0696e700028dac4de106ab14661ef8b5f133f7265da3994cf438bd089d2d9504314932d423464a2dfaae331

data/CHANGELOG.md

@@ -1,3 +1,16 @@
+## [2.1.2] 2023-12-17
+
+Changes
+
+- WIP, continued I18n integration. See [2.1.0] for more information.
+- Removed shortcut mappings for all commands (see `dsu help`) to remove dash ("-") preceeding command shortcuts. For example, `dsu -a` (i.e. shortcut for `dsu add`) is now `dsu a`, `dsu -c` (i.e. shortcut for `dsu config`) is now `dsu c`, etc. This was done to avoid confusion as this format is typically used for options, not shortcut commands. The only exception is `dsu version` which will accept shortcuts `dsu v` and `dsu -v`, as `-v` is generally used to display version information.
+- Various code refactors.
+- Massive updates to README.md.
+
+Bug fixes
+
+- Fix bug that did not apply the current theme to `dsu help add` help.
+
 ## [2.1.1] 2023-12-17
 
 Bug fixes
@@ -17,6 +30,7 @@ Bug fixes
 
 Miscellaneous
 
+- WIP, begin I18n support/integration.
 - Update ruby gems.
 - Updated README.md to reflect new `dsu delete` command.
 - Fix rubocop violations.
@@ -112,11 +126,11 @@ See previous alpha releases for changes.
 
 Changes
 
-- For convenience, the `dsu list date` command now takes a MNEUMONIC in addition to a DATE. See `dsu list help date` for more information.
+- For convenience, the `dsu list date` command now takes a MNEMONIC in addition to a DATE. See `dsu list help date` for more information.
 
 Bug fixes
 
-- Fix a bug that did not display `dsu list dates SUBCOMMAND` date list properly when the `--from` option was a date mneumonic and the `--to` optoin was a relative time mneumonic (e.g. `dsu list dates -f today -t +1`). In this case, DSU dates `Time.now` and `Time.now.tomorrow` should be displayed; instead, the bug would consider the `--to` option as relative to `Time.now`, so only 1 DSU date (`Time.now` would be returned).
+- Fix a bug that did not display `dsu list dates SUBCOMMAND` date list properly when the `--from` option was a date mnemonic and the `--to` optoin was a relative time mnemonic (e.g. `dsu list dates -f today -t +1`). In this case, DSU dates `Time.now` and `Time.now.tomorrow` should be displayed; instead, the bug would consider the `--to` option as relative to `Time.now`, so only 1 DSU date (`Time.now` would be returned).
 
 ## [1.1.0.alpha.1] 2023-05-23
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    dsu (2.1.1)
+    dsu (2.1.2)
       activemodel (>= 7.0.8, < 8.0)
       activesupport (>= 7.0.8, < 8.0)
       colorize (>= 0.8.1, < 1.0)

data/README.md

@@ -1,4 +1,4 @@
-# `dsu`
+# `dsu`- Streamline Your Daily Stand-Up Meeting Participation!
 
 [![GitHub version](http://badge.fury.io/gh/gangelo%2Fdsu.svg)](https://badge.fury.io/gh/gangelo%2Fdsu)
 [![Gem Version](https://badge.fury.io/rb/dsu.svg)](https://badge.fury.io/rb/dsu)
@@ -8,10 +8,25 @@
 
 <img align="center" src="https://i.imgur.com/ff79twF.gif" alt="dsu" />
 
-## About
-`dsu` is a simple, but powerful little gem I wrote for myself to help me manage my Agile DSU (Daily Stand Up) participation. How? by providing a simple command line interface (CLI) which allows me to create, read, update, and delete (CRUD) DSU entries on a daily basis. During my DSU, I'm then able to list, recall and share my DSU activities with my team. DSU entries are grouped by day and are viewed in simple text format from the command line, in a myriad of ways, to meet my personal needs. When viewing DSU entries for a particular day, `dsu` will automatically display the previous day's activities as well, using the typical "what I did yesterday", "What I'm doing today" DSU paradigm. If the DSU date I am trying to view falls on a weekend or Monday, `dsu` will automatically display back to and including the weekend and previous Friday (inclusive), so that I can share what I did over the weekend (if anything) and "last" Friday.
+## Simplify Your Agile Routine
+`dsu` is a sleek and powerful gem that transforms the way you participate in Agile Daily Stand-Ups (DSU). It's designed for developers who love simplicity and efficiency. With `dsu`, you get a user-friendly command-line interface to quickly manage your daily stand-up activities.
 
-You may want to install it and give it a try. If you happen to find `dsu` helpful, give it a star and tell a friend `:)`
+## Why dsu?
+- **Organize Your Tasks:** Easily add, view, update, or delete your DSU entries.
+- **Be Prepared:** Instantly list out your activities for "Yesterday" and plans for "Today" during stand-ups.
+- **Smart Handling of Dates:** `dsu` intelligently includes your weekend and previous Friday activities when necessesary, so you're always ready to share comprehensive updates.
+- **CLI Lovers Rejoice:** If you're a fan of simple command-line tools, `dsu` is a perfect fit.
+
+### Getting Started Is Easy
+Just run `gem install dsu` from your terminal, and you're on your way to more organized and efficient stand-ups. Check out the help section with `$ dsu help` for quick guidance.
+
+## Engage with `dsu`
+Found `dsu` helpful? Star it on GitHub and spread the word! Your feedback and contributions are welcome to make `dsu` even better.
+
+## Quick Install
+```shell
+gem install dsu
+```
 
 ## Help
 
@@ -21,69 +36,87 @@ After installation (`gem install dsu`), the first thing you may want to do is ru
 ```shell
 #=>
 Commands:
-  dsu add|-a [OPTIONS] DESCRIPTION  # Adds a DSU entry...
-  dsu config|-c SUBCOMMAND          # Manage configuration...
-  dsu delete|-d SUBCOMMAND          # Delete DSU entries...
-  dsu edit|-e SUBCOMMAND            # Edit DSU entries...
-  dsu help [COMMAND]                # Describe available...
-  dsu info|-i                       # Displays information...
-  dsu list|-l SUBCOMMAND            # Displays DSU entries...
-  dsu theme|-t SUBCOMMAND           # Manage DSU themes...
-  dsu version|-v                    # Displays this gem version
+  dsu add|a [OPTIONS] DESCRIPTION  # Adds a DSU entry...
+  dsu config|c SUBCOMMAND          # Manage configuration...
+  dsu delete|d SUBCOMMAND          # Delete DSU entries...
+  dsu edit|e SUBCOMMAND            # Edit DSU entries...
+  dsu help [COMMAND]               # Describe available...
+  dsu info|i                       # Displays information...
+  dsu list|l SUBCOMMAND            # Displays DSU entries...
+  dsu theme|t SUBCOMMAND           # Manage DSU themes...
+  dsu version|-v|v                 # Displays this gem version
 
 Options:
   [--debug], [--no-debug]
 ```
 
-The next thing you may want to do is `add` some DSU activities (entries) for a particular day:
+# Using `dsu`
+The folowing section outlines how to use the `dsu` gem.
 
 ## Adding DSU Entries
+The next thing you may want to do is `add` some DSU activities (entries) for a particular day:
+
 `dsu add [OPTIONS] DESCRIPTION`
+`dsu a [OPTIONS] DESCRIPTION`
 
-Adding DSU entry using this command will _add_ the DSU entry for the given day (or date, `-d`), and also _display_ the given day's (or date's, `-d`) DSU entries, as well as the DSU entries for the previous day relative to the given day or date (`-d`). *NOTE: You cannot add duplicate entry group entries; that is, the entry DESCRIPTION needs to be unique within an entry group.*
+Adding DSU entry using this command will _add_ the DSU entry for the given day or date, and then _display_ the DSU entries for that day or date.
+
+**NOTE:** You cannot add duplicate entries for the same day; that is, entry DESCRIPTIONS need to be unique within an entry group for the given day.
 
 ### Today
-If you need to add a DSU entry to the current day (today), you can use the `-n`|`--today` option. Today (`-n`) is the default; therefore, the `-n` flag is optional when adding DSU entries for the current day:
+If you need to add a DSU entry for the current day (today), you can use the `-n`|`--today` option. Today (`-n`) is the default; therefore, the `-n` flag is optional if you want to add a DSU entry for the _current day_ (today). For example, the below commands will both accomplish the same thing:
 
-`$ dsu add -n|-today "Pair with John on ticket IN-12345"`
+`$ dsu add [-n|--today] "Pair with John on ticket IN-12345"`
+`$ dsu a "Pair with John on ticket IN-12345"`
 
 ### Yesterday
-If for some reason you need to add a DSU entry for yesterday, you can use the `-y`| `--yesterday` option:
+If for some reason you need to add a DSU entry for yesterday, you can use the `-y`| `--yesterday` option. Both of the below commands accomplish the same thing:
 
-`$ dsu add -y|--yesterday "Pick up ticket IN-12345"`
+`$ dsu add --yesterday "Pick up ticket IN-12345"`
+`$ dsu a -y "Pick up ticket IN-12345"`
 
 ### Tomorrow
 If you need to add a DSU entry for tomorrow, you can use the `-t`|`--tomorrow` option:
 
-`$ dsu add -t|--tomorrow "Pick up ticket IN-12345"`
+`$ dsu add --tomorrow "Pick up ticket IN-12345"`
+`$ dsu a -t "Pick up ticket IN-12345"`
 
 ### Miscellaneous Date
 
-Both of the below examples will accomplish the same thing, assuming the current year is 2023; the current year is assumed if omitted:
+Both of the below examples will accomplish the same thing, assuming the current year is 2023; the current year is assumed when omitted:
+
+**NOTE:** When **omitting year**, dates must be entered in `MM/DD` format.
+**NOTE:** When **including year**, dates must be entered in `YYYY/MM/DD` format.
 
-`$ dsu add -d "12/31/2023" "Attend company New Years Coffee Meet & Greet"`
-`$ dsu add -d "12/31" "Attend company New Years Coffee Meet & Greet"`
+`$ dsu add --date 2023/12/31 "Attend New Years Coffee Meet & Greet"`
+`$ dsu a -d 12/31 "Attend New Years Coffee Meet & Greet"`
 
 See the [Dates](#dates) section for more information on acceptable DATE formats used by `dsu`.
 
 ## Displaying DSU Entries
-You can display DSU entries for a particular day or date (`date`) using any of the following commands. When displaying DSU entries for a particular day or date (`date`), `dsu` will display the given day or date's (`date`) DSU entries, as well as the DSU entries for the _previous_ day, relative to the given day or date. If the date or day you are trying to view falls on a weekend or Monday, `dsu` will display back to, and including the weekend and previous Friday inclusive; this is so that you can share what you did over the weekend (if anything) and the previous Friday at your DSU:
+You can display DSU entries for a particular day or date using any of the following commands. When displaying DSU entries for a particular day or date, `dsu` will display the DSU entries for the given day or date, as well as the DSU entries for the _previous_ day, relative to the given day or date. If the given day or date falls on a weekend or Monday, `dsu` will display any entries for the preceeding weekend _and_ Friday; this is so that you can share any activities that occurred over the weekend (if anything) as well as any activities for the previous Friday:
 
-- `$ dsu list today|n`
+- `$ dsu list today`
+- `$ dsu l n` # Equivalent to the above, only using shortcuts
 - `$ dsu list tomorrow|t`
+- `$ dsu l t` # Equivalent to the above, only using shortcuts
 - `$ dsu list yesterday|y`
+- `$ dsu l y` # Equivalent to the above, only using shortcuts
 - `$ dsu list date|d DATE|MNEMONIC`
+- `$ dsu l d DATE|MNEMONIC` # Equivalent to the above, only using shortcuts
 - `$ dsu list dates|dd OPTIONS`
+- `$ dsu l dd OPTIONS` # Equivalent to the above, only using shortcuts
 
 See the [Dates](#dates) section for more information on acceptable DATE formats used by `dsu`.
 See the [Mnemonics](#mnemonics) section for more information on acceptable MNEMONIC rules and formats used by `dsu`.
 
-IMPORTANT: In some cases the behavior RDNs have on some commands are context dependent; in such cases the behavior will be noted in the help appropriate to the command, for example see the following `dsu` command help: `dsu list help date` and `dsu list help dates`.
+**IMPORTANT:** In some cases the behavior _relative date mnemonics_ (RDMs, see the [Mnemonics](#mnemonics) section for more information about RDMs) have on some commands are context dependent; in such cases the behavior will be noted in the help appropriate to the command, for example see the following `dsu` command help: `dsu list help date` and `dsu list help dates`.
 
 ### Examples
 The following displays the entries for "Today", where `Time.now == '2023-05-06 08:54:57.6861 -0400'`
 
 `$ dsu list today`
+`$ dsu l t`
 ```shell
 #=>
 Saturday, (Today) 2023-05-06
@@ -94,47 +127,54 @@ Friday, (Yesterday) 2023-05-05
   2. Attend new hire meet & greet
 ```
 
-`$ dsu list date 5/6/2023`
-`$ dsu list date 5/6`
+`$ dsu list date 5/7/2023`
+`$ dsu list d 2023/7/5`
+`$ dsu l d 7/5` # When omitting YYYY, MM/DD is assumed
 
 ```shell
 #=>
-Saturday, (Today) 2023-05-06
+Wednesday, (Today) 2023-07-05
   1. Blocked for locally failing test IN-12345
 
-Friday, (Yesterday) 2023-05-05
+Tuesday, (Yesterday) 2023-07-04
   1. Pick up ticket IN-12345
   2. Attend new hire meet & greet
 ```
+**NOTE:** If `DATE` (`date`|`d`) falls on a weekend or Monday, `dsu` will display any entries for the preceeding weekend _and_ Friday.
 
 #### Listing Date Ranges
 For more information, see the [Mnemonics](#mnemonics) section for more information on acceptable MNEMONIC rules and formats used by `dsu`.
 
-Output omitted for brevity...
-
-Display the DSU entries for the last 3 days.
-
-`dsu list dates --from yesterday --to -2`
-
-Display the DSU entries for 1/1 to 1/4.
+**NOTE:** Output omitted for brevity...
 
-`dsu list dates --from 1/1 --to +3`
+##### Display the DSU entries for the last 3 days
+`$ dsu list dates --from yesterday --to -2`
+`$ dsu l dd -f y -t -2`
 
-Display the DSU entries for 1/2 to 1/5.
+##### Display the DSU entries for 1/1 to 1/4 for the current year
+`$ dsu list dates --from 1/1 --to +3`
+`$ dsu l dd -f 1/1 -t +3`
 
-`dsu list dates --from 1/5 --to -3`
+##### Display the DSU entries for 1/2 to 1/5
+`$ dsu list dates --from 1/5 --to -3`
+`$ dsu l dd -f 1/5 -t -3`
 
-Display the DSU entries for the last week.
+##### Display the DSU entries for the last week
+`$ dsu list dates --from today --to -6`
+`$ dsu l dd -f n -t -6`
 
-`dsu list dates --from today --to -7`
+##### Display the DSU entries back 1 week from yesterday's date
+`$ dsu list dates --from -7 --to +6`
+`$ dsu l dd -f -7 -t +6`
 
-Display the DSU entries back 1 week from yesterday's date. *This example is silly,* but it illustrates the fact that you can use relative mnemonics for both `--from` and `--to` options. While you *can* use relative mnemonics for both `--from` and `--to` options, there is always a more intuitive way.
+**NOTE:** **The above example is silly,** but it illustrates the fact that you can use relative mnemonics for both `--from` and `--to` options. While you *can* use relative mnemonics for both the `--from` and `--to` options, there is usually a more intuitive way.
 
-`dsu list dates --from -7 --to +6`
+For example:
 
-The above can be accomplished MUCH easier by using the `yesterday` mnemonic. This will display the DSU entries back 1 week from yesterday's date.
+This can be accomplished MUCH easier by using the `yesterday` mnemonic. This will display the DSU entries back 1 week from yesterday's date.
 
-`dsu list dates --from yesterday --to -6`
+`$ dsu list dates --from yesterday --to -6`
+`$ dsu l dd -f y -t -6`
 
 ## Editing DSU Entries
 
@@ -142,14 +182,18 @@ You can edit DSU entry groups by date. `dsu` will allow you to edit a DSU entry
 
 If no entries exist for the DSU date, the editor will open and allow you to add entries for that date. If you have the `:carry_over_entries_to_today` configuration option setting set to `true`, entries from the last DSU date will be copied into the editor for your convenience.
 
-*NOTE: duplicate entries are not allowed; that is, the entry DESCRIPTION need to be unique within an entry group. Non-unique entries will not be added to the entry group. The same holds true for entries whose DESCRIPTION that do not pass validation (between 2 and 256 characters (inclusive) in length).*
+**NOTE:** duplicate entries are not allowed; that is, the entry DESCRIPTION must be unique within an entry group. Non-unique entries will not be added to the entry group. The same holds true for entries whose DESCRIPTION that do not pass validation (between 2 and 256 characters (inclusive) in length).
 
-NOTE: See the "[Customizing the `dsu` Configuration File](#customizing-the-dsu-configuration-file)" section to configure `dsu` to use the editor of your choice and other configuration options to make editing more convenient.
+**NOTE:** See the "[Customizing the `dsu` Configuration File](#customizing-the-dsu-configuration-file)" section to configure `dsu` to use the editor of your choice and other configuration options to make editing more convenient.
 
-- `$ dsu edit today|n`
-- `$ dsu edit tomorrow|t`
-- `$ dsu edit yesterday|y`
-- `$ dsu edit date|d DATE`
+- `$ dsu edit today`
+- `$ dsu e n` # Equivalent to the above, only using shortcuts
+- `$ dsu edit tomorrow`
+- `$ dsu e t` # Equivalent to the above, only using shortcuts
+- `$ dsu edit yesterday`
+- `$ dsu e y` # Equivalent to the above, only using shortcuts
+- `$ dsu edit date DATE`
+- `$ dsu e d DATE` # Equivalent to the above, only using shortcuts
 
 ### Examples
 
@@ -233,39 +277,49 @@ from: Interative planning meeting 11:00AM.
       Interative planning meeting 11:00AM.
 ```
 ## Deleting DSU Entry Groups
-You can delete DSU groups, which will delete all the entries associated with a particular day or date range. When deleting DSU entries for a particular day (`date`, `today`, `tomorrow`, `yesterday`), or date range (`dates`), `dsu` will delete the the entries associated with that day or date range:
+You can delete DSU entry groups; this will delete *all* the entries for the particular day or date range. When deleting DSU entries for a particular day (`date`, `today`, `tomorrow`, `yesterday`), or date range (`dates`), `dsu` will delete the entry group(s) and *all* the associated entries for that day or date range:
 
-- `$ dsu delete today|n`
-- `$ dsu delete tomorrow|t`
-- `$ dsu delete yesterday|y`
-- `$ dsu delete date|d DATE|MNEMONIC`
-- `$ dsu delete dates|dd OPTIONS`
+- `$ dsu delete today`
+- `$ dsu d n` # Equivalent to the above, only using shortcuts
+- `$ dsu delete tomorrow`
+- `$ dsu d t` # Equivalent to the above, only using shortcuts
+- `$ dsu delete yesterday`
+- `$ dsu d y` # Equivalent to the above, only using shortcuts
+- `$ dsu delete date DATE|MNEMONIC`
+- `$ dsu d d DATE|MNEMONIC` # Equivalent to the above, only using shortcuts
+- `$ dsu delete dates OPTIONS`
+- `$ dsu d dd OPTIONS` # Equivalent to the above, only using shortcuts
 
-NOTE: Before any `dsu` command is executed to delete an entry group, `dsu` will prompt you to confirm your action; you can continue ('y') or cancel ('N').
+**NOTE:** Before any of the above `dsu` commands are executed, `dsu` will prompt you to confirm the delete; you can continue ('y') or cancel ('N').
 
 See the [Dates](#dates) section for more information on acceptable DATE formats used by `dsu`.
 See the [Mnemonics](#mnemonics) section for more information on acceptable MNEMONIC rules and formats used by `dsu`.
 
-IMPORTANT: In some cases the behavior RDNs have on some commands are context dependent; in such cases the behavior will be noted in the help appropriate to the command, for example see the following `dsu` command help: `dsu delete help date` and `dsu delete help dates`.
+**IMPORTANT:** In some cases the behavior that _relative date mnemonics_ (RDMs, see the [Mnemonics](#mnemonics) section for more information about RDMs) have on some commands are context dependent; in such cases the behavior will be noted in the help appropriate to the command, for example see the following `dsu` command help: `dsu delete help date` and `dsu delete help dates`.
 
 ### Examples
-The following deletes the entry group and all entries for today's date, yesterday's date, and tomorrow's date respectfully.
+The following example deletes the entry group and *all* entries for today's date.
 
 `$ dsu delete today`
+`$ dsu d n`
 ```shell
 #=>
 Are you sure you want to delete all the entries for 2023-12-17 (1 entry groups)? [y/N]> y
 Deleted 1 entry group(s).
 ```
+The following example deletes the entry group and *all* entries for yesterday's date.
 
 `$ dsu delete yesterday`
+`$ dsu d y`
 ```shell
 #=>
 Are you sure you want to delete all the entries for 2023-12-16 (1 entry groups)? [y/N]> y
 Deleted 1 entry group(s).
 ```
+The following example deletes the entry group and *all* entries for tomorrow's date.
 
 `$ dsu delete tomorrow`
+`$ dsu d t`
 ```shell
 #=>
 Are you sure you want to delete all the entries for 2023-12-18 (1 entry groups)? [y/N]> y
@@ -275,6 +329,7 @@ Deleted 1 entry group(s).
 The following deletes the entry group and all entries for 12/17 of the current year.
 
 `$ dsu delete date 12/17`
+`$ dsu d d 12/17`
 ```shell
 #=>
 Are you sure you want to delete all the entries for 2023-12-17 (0 entry groups)? [y/N]> y
@@ -284,14 +339,16 @@ Deleted 1 entry group(s)
 The following deletes the entry group and all entries for the past week, starting from today (12/17/2023).
 
 `$ dsu delete dates --from today --to -6`
+`$ dsu d dd -f n -t -6`
 ```shell
 #=>
 Are you sure you want to delete all the entries for 2023-12-11 thru 2023-12-17 (7 entry groups)? [y/N]> y
 Deleted 7 entry group(s).
 ```
 ## Customizing the `dsu` Configuration File
+To customize the `dsu` configuration file, you may follow the instructions outlined here. It is only recommended that you customize the `dsu` configuration file *only* if you are working with an official release (`n.n.n.n`).
 
-It is **not** recommended that you get too attached to the `dsu` configuration options when this gem is in pre-release (e.g. `n.n.n.alpha.n`, `n.n.n.beta.n`, etc.). This is because changes to the configuration file options could change; however, if you're curious, ambitious, or just like living on the edge, have at it. However, just keep in mind that things could change. With an official release (`n.n.n.n`), edit all you want. Regardless, if you *do* want to customize the `dsu` configuration file, you may do the following:
+**NOTE:** It is **not** recommended that you get too attached to the `dsu` configuration options when this gem is in **pre-release** (e.g. `n.n.n.alpha.n`, `n.n.n.beta.n`, etc.). This is because changes to the configuration file options, of course, could change. With an official release (`n.n.n.n`), edit all you want!
 
 ### Customizing the `dsu` Configuration File
 
@@ -360,18 +417,9 @@ A *mnemonic* may be any of the following: `n|today|t|tomorrow|y|yesterday|+n|-n`
 
 Where `n`, `t`, `y` are aliases for `today`, `tomorrow`, and `yesterday`, respectively.
 
-Where `+n`, `-n` are relative date mnemonics (RDNs). Generally speaking, RDNs are relative to the current date. For example, a RDN of `+1` would be equal to `Time.now + 1.day` (or tomorrow), and a RDN of `-1` would be equal to `Time.now - 1.day` (or yesterday).
-
-NOTE: In some cases the behavior RDNs have on some commands are context dependent; in such cases the behavior will be noted in the help appropriate to the command, for example see the following `dsu` command help: `dsu list help date` and `dsu list help dates`.
-
-
-## Installation
-
-    $ gem install dsu
-
-## Usage
+Where `+n`, `-n` are relative date mnemonics (RDMs). Generally speaking, RDMs are relative to the current date. For example, a RDM of `+1` would be equal to `Time.now + 1.day` (or tomorrow), and a RDM of `-1` would be equal to `Time.now - 1.day` (or yesterday).
 
-TODO: Write usage instructions here (see the [Quick Start](#quick-start) for now)
+NOTE: In some cases the behavior RDMs have on some commands are context dependent; in such cases the behavior will be noted in the help appropriate to the command, for example see the following `dsu` command help: `dsu list help date` and `dsu list help dates`.
 
 ## Development
 

data/lib/dsu/base_cli.rb

@@ -42,8 +42,8 @@ module Dsu
         I18n.t('options.date_option_description')
       end
 
-      def mneumonic_option_description
-        I18n.t('options.mneumonic_option_description')
+      def mnemonic_option_description
+        I18n.t('options.mnemonic_option_description')
       end
     end
 

data/lib/dsu/cli.rb

@@ -12,31 +12,30 @@ require_relative 'subcommands/theme'
 module Dsu
   # The `dsu` command.
   class CLI < BaseCLI
-    # TODO: I18n these mappings.
-    map %w[a -a] => :add
-    map %w[c -c] => :config
-    map %w[d -d] => :delete
-    map %w[e -e] => :edit
-    map %w[l -l] => :list
-    map %w[t -t] => :theme
-    map %w[i -i] => :info
-    map %w[v -v] => :version
+    map I18n.t('commands.add.key_mappings') => :add
+    map I18n.t('commands.config.key_mappings') => :config
+    map I18n.t('commands.delete.key_mappings') => :delete
+    map I18n.t('commands.edit.key_mappings') => :edit
+    map I18n.t('commands.help.key_mappings') => :help
+    map I18n.t('commands.info.key_mappings') => :info
+    map I18n.t('commands.list.key_mappings') => :list
+    map I18n.t('commands.theme.key_mappings') => :theme
+    map I18n.t('commands.version.key_mappings') => :version
 
     desc I18n.t('commands.add.desc'), I18n.t('commands.add.usage')
     long_desc I18n.t('commands.add.long_desc', date_option_description: date_option_description)
-    # TODO: I18n these option aliases.
-    option :date, type: :string, aliases: '-d'
-    option :tomorrow, type: :boolean, aliases: '-t'
-    option :yesterday, type: :boolean, aliases: '-y'
-    option :today, type: :boolean, aliases: '-n', default: true
+    option I18n.t('options.date.name'), aliases: I18n.t('options.date.aliases'), type: :string
+    option I18n.t('options.tomorrow.name'), aliases: I18n.t('options.tomorrow.aliases'), type: :boolean
+    option I18n.t('options.yesterday.name'), aliases: I18n.t('options.yesterday.aliases'), type: :boolean
+    option I18n.t('options.today.name'), aliases: I18n.t('options.today.aliases'), type: :boolean, default: true
     def add(description)
-      time = if options[:date].present?
-        Time.parse(options[:date])
-      elsif options[:tomorrow].present?
+      time = if options[I18n.t('options.date.name')].present?
+        Time.parse(options[I18n.t('options.date.name')])
+      elsif options[I18n.t('options.tomorrow.name')].present?
         Time.now.tomorrow
-      elsif options[:yesterday].present?
+      elsif options[I18n.t('options.yesterday.name')].present?
         Time.now.yesterday
-      elsif options[:today].present?
+      elsif options[I18n.t('options.today.name')].present?
         Time.now
       end
       entry = Models::Entry.new(description: description)

data/lib/dsu/subcommands/base_subcommand.rb

@@ -2,13 +2,11 @@
 
 require_relative '../base_cli'
 require_relative '../support/ask'
-require_relative '../support/subcommand_help_colorizeable'
 
 module Dsu
   module Subcommands
     class BaseSubcommand < Dsu::BaseCLI
       include Support::Ask
-      include Support::SubcommandHelpColorizable
     end
   end
 end

data/lib/dsu/subcommands/delete.rb

@@ -3,7 +3,7 @@
 require_relative '../services/entry_group/counter_service'
 require_relative '../services/entry_group/deleter_service'
 require_relative '../support/command_options/dsu_times'
-require_relative '../support/command_options/time_mneumonic'
+require_relative '../support/command_options/time_mnemonic'
 require_relative '../support/time_formatable'
 require_relative '../views/entry_group/shared/no_entries_to_display'
 require_relative '../views/shared/error'
@@ -12,7 +12,7 @@ require_relative 'base_subcommand'
 module Dsu
   module Subcommands
     class Delete < BaseSubcommand
-      include Support::CommandOptions::TimeMneumonic
+      include Support::CommandOptions::TimeMnemonic
       include Support::TimeFormatable
 
       map %w[d] => :date
@@ -45,13 +45,13 @@ module Dsu
       desc I18n.t('subcommands.delete.date.desc'), I18n.t('subcommands.delete.date.usage')
       long_desc I18n.t('subcommands.delete.date.long_desc',
         date_option_description: date_option_description,
-        mneumonic_option_description: mneumonic_option_description)
+        mnemonic_option_description: mnemonic_option_description)
       option :prompts, type: :hash, default: {}, hide: true, aliases: '-p'
-      def date(date_or_mneumonic)
-        time = if time_mneumonic?(date_or_mneumonic)
-          time_from_mneumonic(command_option: date_or_mneumonic)
+      def date(date_or_mnemonic)
+        time = if time_mnemonic?(date_or_mnemonic)
+          time_from_mnemonic(command_option: date_or_mnemonic)
         else
-          Time.parse(date_or_mneumonic)
+          Time.parse(date_or_mnemonic)
         end
         delete_entry_groups_if times: [time], options: options
       rescue ArgumentError => e
@@ -61,7 +61,7 @@ module Dsu
       desc I18n.t('subcommands.delete.dates.desc'), I18n.t('subcommands.delete.dates.usage')
       long_desc I18n.t('subcommands.delete.dates.long_desc',
         date_option_description: date_option_description,
-        mneumonic_option_description: mneumonic_option_description)
+        mnemonic_option_description: mnemonic_option_description)
       option :from, type: :string, required: true, aliases: '-f', banner: 'DATE|MNEMONIC'
       option :to, type: :string, required: true, aliases: '-t', banner: 'DATE|MNEMONIC'
       option :prompts, type: :hash, default: {}, hide: true, aliases: '-p'

data/lib/dsu/subcommands/list.rb

@@ -2,7 +2,7 @@
 
 require_relative '../services/entry_group/counter_service'
 require_relative '../support/command_options/dsu_times'
-require_relative '../support/command_options/time_mneumonic'
+require_relative '../support/command_options/time_mnemonic'
 require_relative '../support/time_formatable'
 require_relative '../views/entry_group/shared/no_entries_to_display'
 require_relative '../views/shared/error'
@@ -11,7 +11,7 @@ require_relative 'base_subcommand'
 module Dsu
   module Subcommands
     class List < BaseSubcommand
-      include Support::CommandOptions::TimeMneumonic
+      include Support::CommandOptions::TimeMnemonic
       include Support::TimeFormatable
 
       map %w[d] => :date
@@ -47,12 +47,12 @@ module Dsu
       desc I18n.t('subcommands.list.date.desc'), I18n.t('subcommands.list.date.usage')
       long_desc I18n.t('subcommands.list.date.long_desc',
         date_option_description: date_option_description,
-        mneumonic_option_description: mneumonic_option_description)
-      def date(date_or_mneumonic)
-        time = if time_mneumonic?(date_or_mneumonic)
-          time_from_mneumonic(command_option: date_or_mneumonic)
+        mnemonic_option_description: mnemonic_option_description)
+      def date(date_or_mnemonic)
+        time = if time_mnemonic?(date_or_mnemonic)
+          time_from_mnemonic(command_option: date_or_mnemonic)
         else
-          Time.parse(date_or_mneumonic)
+          Time.parse(date_or_mnemonic)
         end
         times = sorted_dsu_times_for(times: [time, time.yesterday])
         view_list_for(times: times, options: options)
@@ -63,10 +63,10 @@ module Dsu
       desc I18n.t('subcommands.list.dates.desc'), I18n.t('subcommands.list.dates.usage')
       long_desc I18n.t('subcommands.list.dates.long_desc',
         date_option_description: date_option_description,
-        mneumonic_option_description: mneumonic_option_description)
+        mnemonic_option_description: mnemonic_option_description)
       option :from, type: :string, required: true, aliases: '-f', banner: 'DATE|MNEMONIC'
       option :to, type: :string, required: true, aliases: '-t', banner: 'DATE|MNEMONIC'
-      option :include_all, default: false, type: :boolean, aliases: '-a', desc: I18n.t('cli.options.include_all')
+      option :include_all, default: false, type: :boolean, aliases: '-a', desc: I18n.t('options.include_all')
       def dates
         options = configuration.to_h.merge(self.options).with_indifferent_access
         times, errors = Support::CommandOptions::DsuTimes.dsu_times_for(from_option: options[:from], to_option: options[:to]) # rubocop:disable Layout/LineLength

data/lib/dsu/support/command_help_colorizeable.rb

@@ -12,11 +12,18 @@ module Dsu
         end
 
         module ClassMethods
+          # Handles general help colorization.
           def help(shell, subcommand = false) # rubocop:disable Style/OptionalBooleanParameter
             help_text = Services::StdoutRedirectorService.call { super }
             puts apply_theme(help_text, theme_color: color_theme.help)
           end
 
+          # Handles sub-command help colorization.
+          def command_help(shell, subcommand = false) # rubocop:disable Style/OptionalBooleanParameter
+            help_text = Services::StdoutRedirectorService.call { super }
+            puts apply_theme(help_text, theme_color: color_theme.help)
+          end
+
           def color_theme
             @color_theme ||= Models::ColorTheme.current_or_default
           end

data/lib/dsu/support/command_options/dsu_times.rb

@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 require_relative 'time'
-require_relative 'time_mneumonic'
+require_relative 'time_mnemonic'
 
 module Dsu
   module Support
@@ -11,7 +11,7 @@ module Dsu
 
         # Returns an array of Time objects. The first element is the "from" time.
         # The second element is the "to" time. Both arguments are expected to be
-        # command options that are time strings, time or relative time mneumonics.
+        # command options that are time strings, time or relative time mnemonics.
         def dsu_times_for(from_option:, to_option:)
           from_time = dsu_from_time_for(from_option: from_option)
           to_time = dsu_to_time_for(to_option: to_option, from_time: from_time)
@@ -28,17 +28,17 @@ module Dsu
         def dsu_from_time_for(from_option:)
           return if from_option.nil?
 
-          from_time = if TimeMneumonic.time_mneumonic?(from_option)
-            TimeMneumonic.time_from_mneumonic(command_option: from_option)
+          from_time = if TimeMnemonic.time_mnemonic?(from_option)
+            TimeMnemonic.time_from_mnemonic(command_option: from_option)
           end
           from_time || Time.time_from_date_string(command_option: from_option)
         end
 
         def dsu_to_time_for(to_option:, from_time:)
-          to_time = if TimeMneumonic.relative_time_mneumonic?(to_option)
-            TimeMneumonic.time_from_mneumonic(command_option: to_option, relative_time: from_time)
-          elsif TimeMneumonic.time_mneumonic?(to_option)
-            TimeMneumonic.time_from_mneumonic(command_option: to_option)
+          to_time = if TimeMnemonic.relative_time_mnemonic?(to_option)
+            TimeMnemonic.time_from_mnemonic(command_option: to_option, relative_time: from_time)
+          elsif TimeMnemonic.time_mnemonic?(to_option)
+            TimeMnemonic.time_from_mnemonic(command_option: to_option)
           end
           to_time || Time.time_from_date_string(command_option: to_option)
         end

data/lib/dsu/support/command_options/time_mnemonic.rb

@@ -0,0 +1,108 @@
+# frozen_string_literal: true
+
+require_relative 'time_mnemonics'
+
+module Dsu
+  module Support
+    module CommandOptions
+      # The purpose of this module is to take a command option that is a string and return a Time object.
+      # The command option is expected to be a time mneumoic.
+      module TimeMnemonic
+        include TimeMnemonics
+
+        module_function
+
+        def time_from_mnemonic(command_option:, relative_time: nil)
+          time_from_mnemonic!(command_option: command_option, relative_time: relative_time)
+        rescue ArgumentError
+          nil
+        end
+
+        # command_option: is expected to me a time mnemonic. If relative_time is NOT nil, all
+        # time mnemonics are relative to relative_time. Otherwise, they are relative to Time.now.
+        # relative_time: is a Time object that is required IF command_option is expected to be
+        # a relative time mnemonic. Otherwise, it is optional.
+        def time_from_mnemonic!(command_option:, relative_time: nil)
+          validate_argument!(command_option: command_option, command_option_name: :command_option)
+          unless relative_time.nil? || relative_time.is_a?(::Time)
+            raise ArgumentError, "relative_time is not a Time object: \"#{relative_time}\""
+          end
+
+          relative_time ||= ::Time.now
+
+          time_for_mnemonic(mnemonic: command_option, relative_time: relative_time)
+        end
+
+        # This method returns true if mnemonic is a valid mnemonic OR
+        # a relative time mnemonic.
+        def time_mnemonic?(mnemonic)
+          mnemonic?(mnemonic) || relative_time_mnemonic?(mnemonic)
+        end
+
+        # This method returns true if mnemonic is a valid relative
+        # time mnemonic.
+        def relative_time_mnemonic?(mnemonic)
+          return false unless mnemonic.is_a?(String)
+
+          mnemonic.match?(RELATIVE_REGEX)
+        end
+
+        # Add private_class_methods here.
+
+        # Returns a Time object from a mnemonic.
+        def time_for_mnemonic(mnemonic:, relative_time:)
+          time = relative_time
+          if today_mnemonic?(mnemonic)
+            time
+          elsif tomorrow_mnemonic?(mnemonic)
+            time.tomorrow
+          elsif yesterday_mnemonic?(mnemonic)
+            time.yesterday
+          elsif relative_time_mnemonic?(mnemonic)
+            relative_time_for(days_from_now: mnemonic, time: time)
+          end
+        end
+
+        def relative_time_for(days_from_now:, time:)
+          days_from_now.to_i.days.from_now(time)
+        end
+
+        # This method returns true if mnemonic is a valid time mnemonic.
+        # This method will return false if mnemonic is an invalid mnemonic
+        # OR if mnemonic is a relative time mnemonic.
+        def mnemonic?(mnemonic)
+          today_mnemonic?(mnemonic) ||
+            tomorrow_mnemonic?(mnemonic) ||
+            yesterday_mnemonic?(mnemonic)
+        end
+
+        def today_mnemonic?(mnemonic)
+          TODAY.include?(mnemonic)
+        end
+
+        def tomorrow_mnemonic?(mnemonic)
+          TOMORROW.include?(mnemonic)
+        end
+
+        def yesterday_mnemonic?(mnemonic)
+          YESERDAY.include?(mnemonic)
+        end
+
+        def validate_argument!(command_option:, command_option_name:)
+          raise ArgumentError, "#{command_option_name} cannot be nil." if command_option.nil?
+          raise ArgumentError, "#{command_option_name} cannot be blank." if command_option.blank?
+          unless command_option.is_a?(String)
+            raise ArgumentError, "#{command_option_name} must be a String: \"#{command_option}\""
+          end
+          unless time_mnemonic?(command_option)
+            raise ArgumentError, "#{command_option_name} is an invalid mnemonic: \"#{command_option}\"."
+          end
+        end
+
+        private_class_method :time_for_mnemonic, :relative_time_for,
+          :mnemonic?, :today_mnemonic?, :tomorrow_mnemonic?,
+          :yesterday_mnemonic?, :validate_argument!
+      end
+    end
+  end
+end

data/lib/dsu/support/command_options/{time_mneumonics.rb → time_mnemonics.rb}

@@ -3,7 +3,7 @@
 module Dsu
   module Support
     module CommandOptions
-      module TimeMneumonics
+      module TimeMnemonics
         # TODO: I18n.
         TODAY = %w[n today].freeze
         TOMORROW = %w[t tomorrow].freeze

data/lib/dsu/version.rb

@@ -2,5 +2,5 @@
 
 module Dsu
   VERSION_REGEX = /\A\d+\.\d+\.\d+(\.alpha\.\d+)?\z/
-  VERSION = '2.1.1'
+  VERSION = '2.1.2'
 end

data/lib/locales/en/commands.yml

@@ -1,15 +1,38 @@
 # lib/dsu/cli.rb
+#
+# NOTE:
+#
+# Commands should have the following layout:
+#
+# en:
+#   commands:
+#     my_command:
+#       key_mappings: thor key mappings
+#       desc:         thor command description
+#       usage:        thor command usage
+#       long_desc:    thor long description
+#
+# Place key_mappings: at the top of the command entries:
+#
+# en:
+#   commands:
+#     my_command:
+#       key_mappings: m # Single mapping
+#       key_mappings:   # Array of mappings
+#         - 'm'
+#         - '-m'
 en:
   commands:
     add:
-      desc: add|-a [OPTIONS] DESCRIPTION
+      key_mappings: a
+      desc: add|a [OPTIONS] DESCRIPTION
       usage: Adds a DSU entry having DESCRIPTION to the date associated with the given OPTION
       long_desc: |
         Will add a DSU entry having DESCRIPTION to the date associated with the given OPTION.
 
         $ dsu add [-d DATE|-n|-t|-y] DESCRIPTION
 
-        $ dsu -a [-d DATE|-n|-t|-y] DESCRIPTION
+        $ dsu a [-d DATE|-n|-t|-y] DESCRIPTION
 
         OPTIONS:
 
@@ -27,16 +50,20 @@ en:
 
         Must be be between 2 and 256 characters (inclusive) in length.
     config:
-      desc: config|-c SUBCOMMAND
+      key_mappings: c
+      desc: config|c SUBCOMMAND
       usage: Manage configuration file for this gem
     delete:
-      desc: delete|-d SUBCOMMAND
+      key_mappings: c
+      desc: delete|d SUBCOMMAND
       usage: Delete DSU entries for the given SUBCOMMAND
     edit:
-      desc: edit|-e SUBCOMMAND
+      desc: edit|e SUBCOMMAND
       usage: Edit DSU entries for the given SUBCOMMAND
+      key_mappings: e
     info:
-      desc: info|-i
+      key_mappings: i
+      desc: info|i
       usage: Displays information about this DSU release
       info: |
         Dsu Info
@@ -56,15 +83,34 @@ en:
          Migration version folder: %{migration_version_folder}
             Migration file folder: %{migration_file_folder}
     list:
-      desc: list|-l SUBCOMMAND
+      key_mappings: l
+      desc: list|l SUBCOMMAND
       usage: Displays DSU entries for the given SUBCOMMAND
     theme:
-      desc: theme|-t SUBCOMMAND
+      key_mappings: t
+      desc: theme|t SUBCOMMAND
       usage: Manage DSU themes
     version:
-      desc: version|-v
+      key_mappings:
+        - v
+        - '-v'
+      desc: version|v|-v
       usage: Displays the DSU version for this gem
+  # Should these options go under their respective commands
+  # (e.g. commands.options.date.name, commands.options.today.aliases, etc.)?
   options:
+    date:
+      aliases: -d
+      name: 'date'
+    today:
+      aliases: -n
+      name: 'today'
+    tomorrow:
+      aliases: -t
+      name: 'tomorrow'
+    yesterday:
+      aliases: -y
+      name: 'yesterday'
     include_all: Include dates that have no DSU entries
     date_option_description: |
       DATE
@@ -74,17 +120,17 @@ en:
       as well as omit the year if the date you want to display is the
       current year (e.g. <month>/<day>, or 1/31). For example: `require 'time';
       Time.parse('01/02/2023'); Time.parse('1/2') # etc.`
-    mneumonic_option_description: |
-      MNEUMONIC
+    mnemonic_option_description: |
+      MNEMONIC
 
       This may be any of the following: n|today|t|tomorrow|y|yesterday|+n|-n.
 
       Where n, t, y are aliases for today, tomorrow, and yesterday, respectively.
 
-      Where +n, -n are relative date mneumonics (RDNs). Generally speaking,
-      RDNs are relative to the current date. For example, a RDN of +1 would be
-      equal to `Time.now + 1.day` (tomorrow), and a RDN of -1 would be equal to
+      Where +n, -n are relative date mnemonics (RDMs). Generally speaking,
+      RDMs are relative to the current date. For example, a RDM of +1 would be
+      equal to `Time.now + 1.day` (tomorrow), and a RDM of -1 would be equal to
       `Time.now - 1.day` (yesterday).
 
-      In some cases the behavior RDNs have on some commands are context dependent;
+      In some cases the behavior RDMs have on some commands are context dependent;
       in such cases the behavior will be noted.

data/lib/locales/en/subcommands.yml

@@ -71,14 +71,14 @@ en:
           Default: "default"
     delete:
       date:
-        desc: date|d DATE|MNEUMONIC
-        usage: Deletes the DSU entries for the given DATE or MNEUMONIC
+        desc: date|d DATE|MNEMONIC
+        usage: Deletes the DSU entries for the given DATE or MNEMONIC
         long_desc: |
-          Deletes the DSU entries for the given DATE or MNEUMONIC.
+          Deletes the DSU entries for the given DATE or MNEMONIC.
 
           %{date_option_description}
 
-          %{mneumonic_option_description}
+          %{mnemonic_option_description}
       dates:
         desc: dates|dd OPTIONS
         usage: Deletes the DSU entries for the OPTIONS provided
@@ -91,13 +91,13 @@ en:
 
           OPTIONS:
 
-          -f|--from DATE|MNEMONIC: The DATE or MNEUMONIC that represents the start of the range of DSU dates to delete. If a relative mneumonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the current date (e.g. `<MNEUMONIC>.to_i.days.from_now(Time.now)`).
+          -f|--from DATE|MNEMONIC: The DATE or MNEMONIC that represents the start of the range of DSU dates to delete. If a relative mnemonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the current date (e.g. `<MNEMONIC>.to_i.days.from_now(Time.now)`).
 
-          -t|--to DATE|MNEMONIC: The DATE or MNEUMONIC that represents the end of the range of DSU dates to delete. If a relative mneumonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the date that resulting from the `--from` option date calculation.
+          -t|--to DATE|MNEMONIC: The DATE or MNEMONIC that represents the end of the range of DSU dates to delete. If a relative mnemonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the date that resulting from the `--from` option date calculation.
 
           %{date_option_description}
 
-          %{mneumonic_option_description}
+          %{mnemonic_option_description}
 
           EXAMPLES:
 
@@ -116,15 +116,15 @@ en:
           $ dsu delete dates --from today --to -7
 
           This (assuming "today" is 5/23) will delete the DSU entries for the last week 5/16 to 5/22.
-          This example simply illustrates the fact that you can use relative mneumonics for
+          This example simply illustrates the fact that you can use relative mnemonics for
           both `--from` and `--to` options; this doesn't mean you should do so...
 
-          While you can use relative mneumonics for both `--from` and `--to` options,
+          While you can use relative mnemonics for both `--from` and `--to` options,
           there is always a more intuitive way. The below example basically deletes one week of DSU entries back 1 week from yesterday's date:
 
           $ dsu delete dates --from -7 --to +6
 
-          The above can be accomplished MUCH easier by simply using the `yesterday` mneumonic...
+          The above can be accomplished MUCH easier by simply using the `yesterday` mnemonic...
 
           This (assuming "today" is 5/23) will delete the DSU entries back 1 week from yesterday's date 5/16 to 5/22:
 
@@ -186,14 +186,14 @@ en:
           Edits the DSU entries for yesterday.
     list:
       date:
-        desc: date|d DATE|MNEUMONIC
-        usage: Displays the DSU entries for the given DATE or MNEUMONIC
+        desc: date|d DATE|MNEMONIC
+        usage: Displays the DSU entries for the given DATE or MNEMONIC
         long_desc: |
-          Displays the DSU entries for the given DATE or MNEUMONIC.
+          Displays the DSU entries for the given DATE or MNEMONIC.
 
           %{date_option_description}
 
-          %{mneumonic_option_description}
+          %{mnemonic_option_description}
       dates:
         desc: dates|dd OPTIONS
         usage: Displays the DSU entries for the OPTIONS provided
@@ -208,13 +208,13 @@ en:
 
           -a|--include-all true|false: If true, all DSU dates within the specified range will be displayed. If false, DSU dates between the first and last DSU dates that have NO entries will NOT be displayed.. The default is taken from the dsu configuration setting :include_all, see `dsu config info`.
 
-          -f|--from DATE|MNEMONIC: The DATE or MNEUMONIC that represents the start of the range of DSU dates to display. If a relative mneumonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the current date (e.g. `<MNEUMONIC>.to_i.days.from_now(Time.now)`).
+          -f|--from DATE|MNEMONIC: The DATE or MNEMONIC that represents the start of the range of DSU dates to display. If a relative mnemonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the current date (e.g. `<MNEMONIC>.to_i.days.from_now(Time.now)`).
 
-          -t|--to DATE|MNEMONIC: The DATE or MNEUMONIC that represents the end of the range of DSU dates to display. If a relative mneumonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the date that resulting from the `--from` option date calculation.
+          -t|--to DATE|MNEMONIC: The DATE or MNEMONIC that represents the end of the range of DSU dates to display. If a relative mnemonic is used (+/-n, e.g +1, -1, etc.), the date calculated will be relative to the date that resulting from the `--from` option date calculation.
 
           %{date_option_description}
 
-          %{mneumonic_option_description}
+          %{mnemonic_option_description}
 
           EXAMPLES:
 
@@ -235,16 +235,16 @@ en:
           $ dsu list dates --from today --to -7
 
           This (assuming "today" is 5/23) will display the DSU entries for the last week 5/16 to 5/22.
-          This example simply illustrates the fact that you can use relative mneumonics for
+          This example simply illustrates the fact that you can use relative mnemonics for
           both `--from` and `--to` options; this doesn't mean you should do so...
 
-          While you can use relative mneumonics for both `--from` and `--to` options,
+          While you can use relative mnemonics for both `--from` and `--to` options,
           there is always a more intuitive way. The below example basically lists one week
           of DSU entries back 1 week from yesterday's date:
 
           $ dsu list dates --from -7 --to +6
 
-          The above can be accomplished MUCH easier by simply using the `yesterday` mneumonic...
+          The above can be accomplished MUCH easier by simply using the `yesterday` mnemonic...
 
           This (assuming "today" is 5/23) will display the DSU entries back 1 week from yesterday's date 5/16 to 5/22:
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dsu
 version: !ruby/object:Gem::Version
-  version: 2.1.1
+  version: 2.1.2
 platform: ruby
 authors:
 - Gene M. Angelo, Jr.
@@ -130,25 +130,14 @@ dependencies:
     - - "<"
       - !ruby/object:Gem::Version
         version: '2.0'
-description: '    dsu is a small, but powerful gem that helps manage your Agile DSU
-  (Daily Stand Up) participation. How? by providing a simple command-line interface
-  (CLI) which allows you to create, read, update, and delete (CRUD) your DSU entries
-  (activities). During your DSU, you can use dsu''s CLI to list and share what you
-  did "yesterday" and what you plan on doing "Today" with your team. DSU entries are
-  grouped by day and can be viewed in simple text format from the command-line. When
-  displaying DSU entries for a particular day, dsu will also display DSU entries for
-  the previous day. If the day you are trying to display falls on a weekend or Monday,
-  dsu will automatically search back to include the weekend and previous Friday dates
-  and display the entries; this is so that you can share what you did over the weekend
-  (if anything) and the previous Friday with your team. When searching for "Yesterday''s"
-  DSU entries, dsu will automatically search back a maximimum of 7 days to find DSU
-  entries to share. This could be helpful if, for example, if you are sharing what
-  you plan to do today (Wednesday), but were sick yesterday (Tuesday); dsu in this
-  case will display the last DSU entries it can find searching backwards a maximum
-  of 7 days. dsu does a LOT more and is perfect for command-line junkies and those
-  who LOVE simplicity. Give it a try and a star if you like it!
-
-  '
+description: "    Get ready to jazz and snazz up your daily stand-ups with dsu, the
+  agile developer's new best friend! This handy command-line gem is all about making
+  your Daily Stand-Up (DSU) participation smooth, fun, and super efficient. Effortlessly
+  create, update, and organize your DSU entries, turning the task of tracking and
+  sharing your daily activities into a breeze. With its intuitive interface and smart
+  date management, dsu ensures you’re always ready to inform your team about your
+  recent progress and upcoming plans. Perfect for command-line tool enthusiasts, dsu
+  brings a dash of simplicity and fun, fun, fun to your daily agile routine!\n"
 email:
 - public.gma@gmail.com
 executables:
@@ -218,14 +207,13 @@ files:
 - lib/dsu/support/command_hookable.rb
 - lib/dsu/support/command_options/dsu_times.rb
 - lib/dsu/support/command_options/time.rb
-- lib/dsu/support/command_options/time_mneumonic.rb
-- lib/dsu/support/command_options/time_mneumonics.rb
+- lib/dsu/support/command_options/time_mnemonic.rb
+- lib/dsu/support/command_options/time_mnemonics.rb
 - lib/dsu/support/descriptable.rb
 - lib/dsu/support/entry_group_viewable.rb
 - lib/dsu/support/field_errors.rb
 - lib/dsu/support/fileable.rb
 - lib/dsu/support/presentable.rb
-- lib/dsu/support/subcommand_help_colorizeable.rb
 - lib/dsu/support/time_comparable.rb
 - lib/dsu/support/time_formatable.rb
 - lib/dsu/support/times_sortable.rb
@@ -278,7 +266,9 @@ post_install_message: |
 
   Dsu now has a delete command! Try it out by running `dsu delete help`.
 
-  Try a dsu theme by running `dsu theme list` and then `dsu theme use THEME_NAME` where THEME_NAME is the name of the theme you want to try :)
+  Try a dsu theme by running `dsu theme list` and then `dsu theme use THEME_NAME` where THEME_NAME is the name of the theme you want to try.
+
+  :)
 rdoc_options: []
 require_paths:
 - lib

data/lib/dsu/support/command_options/time_mneumonic.rb

@@ -1,108 +0,0 @@
-# frozen_string_literal: true
-
-require_relative 'time_mneumonics'
-
-module Dsu
-  module Support
-    module CommandOptions
-      # The purpose of this module is to take a command option that is a string and return a Time object.
-      # The command option is expected to be a time mneumoic.
-      module TimeMneumonic
-        include TimeMneumonics
-
-        module_function
-
-        def time_from_mneumonic(command_option:, relative_time: nil)
-          time_from_mneumonic!(command_option: command_option, relative_time: relative_time)
-        rescue ArgumentError
-          nil
-        end
-
-        # command_option: is expected to me a time mneumonic. If relative_time is NOT nil, all
-        # time mneumonics are relative to relative_time. Otherwise, they are relative to Time.now.
-        # relative_time: is a Time object that is required IF command_option is expected to be
-        # a relative time mneumonic. Otherwise, it is optional.
-        def time_from_mneumonic!(command_option:, relative_time: nil)
-          validate_argument!(command_option: command_option, command_option_name: :command_option)
-          unless relative_time.nil? || relative_time.is_a?(::Time)
-            raise ArgumentError, "relative_time is not a Time object: \"#{relative_time}\""
-          end
-
-          relative_time ||= ::Time.now
-
-          time_for_mneumonic(mneumonic: command_option, relative_time: relative_time)
-        end
-
-        # This method returns true if mneumonic is a valid mneumonic OR
-        # a relative time mneumonic.
-        def time_mneumonic?(mneumonic)
-          mneumonic?(mneumonic) || relative_time_mneumonic?(mneumonic)
-        end
-
-        # This method returns true if mneumonic is a valid relative
-        # time mneumonic.
-        def relative_time_mneumonic?(mneumonic)
-          return false unless mneumonic.is_a?(String)
-
-          mneumonic.match?(RELATIVE_REGEX)
-        end
-
-        # Add private_class_methods here.
-
-        # Returns a Time object from a mneumonic.
-        def time_for_mneumonic(mneumonic:, relative_time:)
-          time = relative_time
-          if today_mneumonic?(mneumonic)
-            time
-          elsif tomorrow_mneumonic?(mneumonic)
-            time.tomorrow
-          elsif yesterday_mneumonic?(mneumonic)
-            time.yesterday
-          elsif relative_time_mneumonic?(mneumonic)
-            relative_time_for(days_from_now: mneumonic, time: time)
-          end
-        end
-
-        def relative_time_for(days_from_now:, time:)
-          days_from_now.to_i.days.from_now(time)
-        end
-
-        # This method returns true if mneumonic is a valid time mneumonic.
-        # This method will return false if mneumonic is an invalid mneumonic
-        # OR if mneumonic is a relative time mneumonic.
-        def mneumonic?(mneumonic)
-          today_mneumonic?(mneumonic) ||
-            tomorrow_mneumonic?(mneumonic) ||
-            yesterday_mneumonic?(mneumonic)
-        end
-
-        def today_mneumonic?(mneumonic)
-          TODAY.include?(mneumonic)
-        end
-
-        def tomorrow_mneumonic?(mneumonic)
-          TOMORROW.include?(mneumonic)
-        end
-
-        def yesterday_mneumonic?(mneumonic)
-          YESERDAY.include?(mneumonic)
-        end
-
-        def validate_argument!(command_option:, command_option_name:)
-          raise ArgumentError, "#{command_option_name} cannot be nil." if command_option.nil?
-          raise ArgumentError, "#{command_option_name} cannot be blank." if command_option.blank?
-          unless command_option.is_a?(String)
-            raise ArgumentError, "#{command_option_name} must be a String: \"#{command_option}\""
-          end
-          unless time_mneumonic?(command_option)
-            raise ArgumentError, "#{command_option_name} is an invalid mneumonic: \"#{command_option}\"."
-          end
-        end
-
-        private_class_method :time_for_mneumonic, :relative_time_for,
-          :mneumonic?, :today_mneumonic?, :tomorrow_mneumonic?,
-          :yesterday_mneumonic?, :validate_argument!
-      end
-    end
-  end
-end

data/lib/dsu/support/subcommand_help_colorizeable.rb

@@ -1,27 +0,0 @@
-# frozen_string_literal: true
-
-require_relative '../models/color_theme'
-require_relative '../support/color_themable'
-
-module Dsu
-  module Support
-    module SubcommandHelpColorizable
-      class << self
-        def included(base)
-          base.extend(ClassMethods)
-        end
-
-        module ClassMethods
-          def command_help(shell, subcommand = false) # rubocop:disable Style/OptionalBooleanParameter
-            help_text = Services::StdoutRedirectorService.call { super }
-            puts apply_theme(help_text, theme_color: color_theme.help)
-          end
-
-          def color_theme
-            @color_theme ||= Models::ColorTheme.current_or_default
-          end
-        end
-      end
-    end
-  end
-end