Merge branch 'feature/bash-logging-filter/BK-2020-02' of https://zdv2.bktei.com/gitwe...

[EVA-2020-02.git] / exec / bklog-plan.org

diff --git a/exec/bklog-plan.org b/exec/bklog-plan.org
index 18bdf42467460ca1e475f87f4d13be4a1e1e97d2..3b7f5f5460fbb0f4a3cfe374515943a577eebaac 100644 (file)
--- a/exec/bklog-plan.org
+++ b/exec/bklog-plan.org
@@ -87,7 +87,14 @@ closed.
 
 *** 2020-07-14T22:25Z; bktei> 
 Possible solution using ~dd~, ~od~, and ~if [ -z string ]~ [[https://unix.stackexchange.com/a/33055][here]].
 
 *** 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
 *** 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