dsu 2.0.8 → 2.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: be24d68c63eb7d876b76151ea9ca595b274497bda51833ce219c9cbc199ea571
-  data.tar.gz: edb7e28872bacb2cb3e339a8f547a4d9c1292446794fc3cbdc4b92c674672c8d
+  metadata.gz: f56239cec153192ff0f815e124e8001ab7676c418f334ff328512c6cfc11eeb4
+  data.tar.gz: d0072d4760663b70d32fa5695c6dbae27db960b95017a0a49598ef53a0bba588
 SHA512:
-  metadata.gz: f74f19a8e0af6bfc3466dce00b534621ac52292b0911850b81fad8b48c9a0e9f86b1ee90ee83a952ea972c542e82da7e77488e2a4d36fe5c13a0526a84185ec8
-  data.tar.gz: 6180f77045935d38c4fbf217964349d47434758ac11c28e79c04b73822204482d020421c79882bfe053c0a86c9832ffc1f2b8054d84cb43b098c5526acb09435
+  metadata.gz: 8e60d02338b12cd52c7f2a0b4f8f5f633879c6c3e7614b8fd1563d03348e778e9cb6f83a674e0be9bf53b5cac878e058d045834ce7c0f615e12129830fc2ca5b
+  data.tar.gz: d6807da2999520c94dbe54b5439b52a386701a20e0696e700028dac4de106ab14661ef8b5f133f7265da3994cf438bd089d2d9504314932d423464a2dfaae331

data/CHANGELOG.md

@@ -1,3 +1,40 @@
+## [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
+
+- Fix bug that did not included I18n locale files in yanked version 2.1.0.
+
+
+## [2.1.0] 2023-12-16
+
+Enhancements
+
+- Added `dsu delete` command to incorporate color themes. See `dsu help delete` for more information.
+
+Bug fixes
+
+- Fix bug that failed to show "(nothing to display for <day>, <date> <local time designator> through <day>, <date> <local time designator>)" for `dsu list dates` command when no entries existed for the entry groups associated with the given dates.
+
+Miscellaneous
+
+- WIP, begin I18n support/integration.
+- Update ruby gems.
+- Updated README.md to reflect new `dsu delete` command.
+- Fix rubocop violations.
+
 ## [2.0.8] 2023-12-02
 
 - Update ruby gems.
@@ -89,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.0.8)
+    dsu (2.1.2)
       activemodel (>= 7.0.8, < 8.0)
       activesupport (>= 7.0.8, < 8.0)
       colorize (>= 0.8.1, < 1.0)
@@ -26,7 +26,7 @@ GEM
       tzinfo (~> 2.0)
     ast (2.4.2)
     base64 (0.2.0)
-    bigdecimal (3.1.4)
+    bigdecimal (3.1.5)
     byebug (11.1.3)
     coderay (1.1.3)
     colorize (0.8.1)
@@ -42,14 +42,14 @@ GEM
     ffaker (2.23.0)
     i18n (1.14.1)
       concurrent-ruby (~> 1.0)
-    json (2.7.0)
+    json (2.7.1)
     kwalify (0.7.2)
     language_server-protocol (3.17.0.3)
     method_source (1.0.0)
     minitest (5.20.0)
     mutex_m (0.2.0)
     os (1.1.4)
-    parallel (1.23.0)
+    parallel (1.24.0)
     parser (3.2.2.4)
       ast (~> 2.4.1)
       racc
@@ -66,7 +66,7 @@ GEM
       kwalify (~> 0.7.0)
       parser (~> 3.2.0)
       rainbow (>= 2.0, < 4.0)
-    regexp_parser (2.8.2)
+    regexp_parser (2.8.3)
     rexml (3.2.6)
     rspec (3.12.0)
       rspec-core (~> 3.12.0)
@@ -81,7 +81,7 @@ GEM
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.12.0)
     rspec-support (3.12.1)
-    rubocop (1.58.0)
+    rubocop (1.59.0)
       json (~> 2.3)
       language_server-protocol (>= 3.17.0)
       parallel (~> 1.10)
@@ -98,9 +98,9 @@ GEM
       rubocop (~> 1.41)
     rubocop-factory_bot (2.24.0)
       rubocop (~> 1.33)
-    rubocop-performance (1.19.1)
-      rubocop (>= 1.7.0, < 2.0)
-      rubocop-ast (>= 0.4.0)
+    rubocop-performance (1.20.0)
+      rubocop (>= 1.48.1, < 2.0)
+      rubocop-ast (>= 1.30.0, < 2.0)
     rubocop-rspec (2.25.0)
       rubocop (~> 1.40)
       rubocop-capybara (~> 2.17)

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)
@@ -6,10 +6,27 @@
 [![Report Issues](https://img.shields.io/badge/report-issues-red.svg)](https://github.com/gangelo/dsu/issues)
 [![License](http://img.shields.io/badge/license-MIT-yellowgreen.svg)](#license)
 
-## 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.
+<img align="center" src="https://i.imgur.com/ff79twF.gif" alt="dsu" />
 
-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 `:)`
+## 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.
+
+## 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
 
@@ -19,68 +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 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 list date|d DATE|MNEUMONIC`
+- `$ 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 [Mneumonics](#mneumonics) section for more information on acceptable MNEUMONIC rules and 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
@@ -91,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 [Mneumonics](#mneumonics) section for more information on acceptable MNEUMONIC rules and formats used by `dsu`.
-
-Output omitted for brevity...
-
-Display the DSU entries for the last 3 days.
+For more information, see the [Mnemonics](#mnemonics) section for more information on acceptable MNEMONIC rules and formats used by `dsu`.
 
-`dsu list dates --from yesterday --to -2`
+**NOTE:** Output omitted for brevity...
 
-Display the DSU entries for 1/1 to 1/4.
+##### Display the DSU entries for the last 3 days
+`$ dsu list dates --from yesterday --to -2`
+`$ dsu l dd -f y -t -2`
 
-`dsu list dates --from 1/1 --to +3`
+##### 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`
 
-Display the DSU entries for 1/2 to 1/5.
+##### 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`
 
-`dsu list dates --from 1/5 --to -3`
+##### Display the DSU entries for the last week
+`$ dsu list dates --from today --to -6`
+`$ dsu l dd -f n -t -6`
 
-Display the DSU entries for the last week.
+##### 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`
 
-`dsu list dates --from today --to -7`
+**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.
 
-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 mneumonics for both `--from` and `--to` options. While you *can* use relative mneumonics for both `--from` and `--to` options, there is always a more intuitive way.
+For example:
 
-`dsu list dates --from -7 --to +6`
+This can be accomplished MUCH easier by using the `yesterday` mnemonic. This will display the DSU entries back 1 week from yesterday's date.
 
-The above can be accomplished MUCH easier by using the `yesterday` mneumonic. 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
 
@@ -139,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
 
@@ -229,10 +276,79 @@ from: Interative planning meeting 11:00AM.
       Pair with Chad on ticket 31211.
       Interative planning meeting 11:00AM.
 ```
+## Deleting DSU Entry Groups
+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`
+- `$ 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 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 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 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
+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
+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
 
@@ -267,6 +383,8 @@ This is the default editor to use when editing entry groups if the EDITOR enviro
 
 Default: `nano` (you'll need to change the default editor on Windows systems)
 
+NOTE: [Visual Studio Code](https://code.visualstudio.com/docs/editor/command-line), users, use `"code --wait"` (or `"code -w"`, short form) to make sure the vscode editor waits for the edited file to be saved and closed before returning control to the dsu process.
+
 ##### entries_display_order
 Valid values are 'asc' and 'desc', and will sort listed DSU entries in ascending or descending order respectfully, by day.
 
@@ -291,26 +409,17 @@ These notes apply to anywhere DATE is used...
 
 DATE may be any date string that can be parsed using `Time.parse`. Consequently, you may 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('2023/01/02'); Time.parse('1/2/2023'); Time.parse('1/2') # etc.`
 
-## Mneumonics
+## Mnemonics
 
-These notes apply to anywhere MNEUMONIC is used...
+These notes apply to anywhere MNEMONIC is used...
 
-A *mneumonic* may be any of the following: `n|today|t|tomorrow|y|yesterday|+n|-n`.
+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 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` (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/core/ruby/color_theme_mode.rb

@@ -36,7 +36,7 @@ module ColorThemeMode
   end
 
   def light!
-    light_color = "light_#{self[:color].to_s.gsub('light_', '')}".to_sym
+    light_color = :"light_#{self[:color].to_s.gsub('light_', '')}"
     dup.merge({ color: light_color })
   end
 end

data/lib/dsu/base_cli.rb

@@ -39,25 +39,11 @@ module Dsu
       end
 
       def date_option_description
-        <<-OPTION_DESC
-          DATE
-
-          This may be any date string that can be parsed using `Time.parse`. Consequently, you may use also use '/' as date separators, as well as omit thee 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.`
-        OPTION_DESC
+        I18n.t('options.date_option_description')
       end
 
-      def mneumonic_option_description
-        <<-OPTION_DESC
-          MNEUMONIC
-
-          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 `Time.now - 1.day` (yesterday).
-
-          In some cases the behavior RDNs have on some commands are context dependent; in such cases the behavior will be noted.
-        OPTION_DESC
+      def mnemonic_option_description
+        I18n.t('options.mnemonic_option_description')
       end
     end