From: Steven Baltakatei Sandoval <baltakatei@gmail.com>
Date: Fri, 16 Oct 2020 22:41:44 +0000 (+0000)
Subject: Merge branch 'feature/bash-logging-filter/BK-2020-02' of https://zdv2.bktei.com/gitwe... 
X-Git-Url: https://zdv2.bktei.com/gitweb/EVA-2020-02.git/commitdiff_plain/a8cd68d3a839a40c0142e61ff3013a70d5e461f7?ds=inline;hp=-c

Merge branch 'feature/bash-logging-filter/BK-2020-02' of https://zdv2.bktei.com/gitweb/ninfacyzga-01 into feature/bash-logging-filter/BK-2020-02
---

a8cd68d3a839a40c0142e61ff3013a70d5e461f7
diff --combined exec/bklog-plan.org
index 9afaea9,18bdf42..3b7f5f5
--- a/exec/bklog-plan.org
+++ b/exec/bklog-plan.org
@@@ -87,13 -87,12 +87,19 @@@ closed
  
  *** 2020-07-14T22:25Z; bktei> 
  Possible solution using ~dd~, ~od~, and ~if [ -z string ]~ [[https://unix.stackexchange.com/a/33055][here]].
 -** TODO Support configuration file
 +** TODO Support configuration file for storing options
 +*** 2020-07-15T23:48Z;bktei>
 +Support storing options in a ~$HOME/.config/bklog/options.conf~ file
 +so individual calls to ~bklog~ don't have to be so long. Aliases can
 +be used instead to make ~bklog~ calls shorter, but cron jobs don't
 +necessarily source alias files. Explicitly reading options from a
 +configuration file would be more reliable, although it complicates
 +usage of ~bklog~.
+ *** 2020-07-20T01:45Z; bktei>
+ It should be possible to specify options via a configuration file
+ stored within a ~~/.config/~ directory instead of specifying options
+ each time ~bklog~ is called. This feature would simplify use of
+ ~bklog~ in situations where specifying options is tiresome and only
+ quick / one-off use of ~bklog~ is needed.
  * bklog narrative