MuranoCLI 3.2.0.beta.1 → 3.2.0.beta.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cb061c736e0642412756d2b964e8dc05a5955863beaa0c94cd5b9cd1f77fd7a6
-  data.tar.gz: d94b914a08a3679c09332d9ade3533d6e9bc350ba9b84656f50890834cf34dcf
+  metadata.gz: aee0c62e2b43c3677482ff5962c744efeb602e2a889aec33f4c25318e14b24d7
+  data.tar.gz: 626bc2a19f7a9d5dccc4943b3710ec75f4b7dcaf75aedb2e8d216f300bc42129
 SHA512:
-  metadata.gz: ccfa0f6a460dd6510919cc82d5482485dc16c88ccf0feb9af2f06408dd07ab6b22526f215aa4f63445264a866f08cad15c4ded3c7b75d8e179ce7d2a60e4900e
-  data.tar.gz: c684535687d90509380929e5e5f014d7e2e1706f20b25560d077e8e58e19c457d7ff027de9c3d0b4ebb72a1e4d5646d2abb3c5e3c9ac477ae6828a0a6c25c9ce
+  metadata.gz: 6cc99cff39c92cbcce0b368bc5cf665eee0d1a296fb62ebed9002fe52b64e5aaa919dfa0696893be838b292f9d275cfa5c387db9befd8327123fa3980b8d4d18
+  data.tar.gz: 8b7234f489e517edc073ce7386426f19f376d04fe8e5694fb60396903a2c2c0f4cecd1452f36835d668e72fd3bfd1355beadb76b22f6132fd60ac906b21161d1

data/.rubocop.yml

@@ -6,7 +6,7 @@
 
 # USAGE:
 #
-#   cd /exo/clients/exosite/MuranoCLI
+#   cd /path/to/MuranoCLI
 #   rubocop -D -c .rubocop.yml
 
 # "Incorrect indentation detected (column X instead of Y)."
@@ -152,6 +152,7 @@ Style/FileName:
     - 'lib/MrMurano/Webservice-Endpoint.rb'
     - 'lib/MrMurano/Webservice-File.rb'
     - 'lib/MrMurano/Webservice.rb'
+    - 'lib/MrMurano/variegated/TruthyFalsey.rb'
     - 'spec/Account-Passwords_spec.rb'
     - 'spec/Account_spec.rb'
     - 'spec/Business_spec.rb'
@@ -164,6 +165,7 @@ Style/FileName:
     - 'spec/GatewayResource_spec.rb'
     - 'spec/GatewaySettings_spec.rb'
     - 'spec/Http_spec.rb'
+    - 'spec/HttpAuthed_spec.rb'
     - 'spec/MakePretties_spec.rb'
     - 'spec/Mock_spec.rb'
     - 'spec/ProjectFile_spec.rb'
@@ -180,6 +182,7 @@ Style/FileName:
     - 'spec/Webservice-Endpoint_spec.rb'
     - 'spec/Webservice-File_spec.rb'
     - 'spec/Webservice-Setting_spec.rb'
+    - 'spec/variegated_TruthyFalsey_spec.rb'
 
 # FIXME/2017-06-30: We should fix this one... put $cfg in MrMurano class.
 # "Do not introduce global variables."

data/.trustme.plugin

@@ -0,0 +1,137 @@
+#!/bin/bash
+# vim:tw=0:ts=2:sw=2:et:norl:spell:ft=sh
+
+assign_globals() {
+  assign_globals_
+}
+
+init_it() {
+  init_it_
+
+  if [[ -f ${HOME}/.fries/lib/ruby_util.sh ]]; then
+    source ${HOME}/.fries/lib/ruby_util.sh
+  else
+    say 'Missing ruby_util.sh and chruby'
+    exit 1
+  fi
+  # FIXME/2017-12-01: Make this more flexible? Allow many versions??
+  # Redirect "Monkey patching!" output.
+  chruby 2.3.3 &> /dev/null
+}
+
+lang_it() {
+  lang_it_
+}
+
+build_it() {
+  build_it_
+
+  say "- cwd        : $(pwd)"
+  say "- ruby -v    : $(ruby -v)"
+  say "- rubocop -v : $(rubocop -v)"
+  #say "- cmd rubocop: $(command -v rubocop)"
+  say
+
+  local projpath="/exo/clients/exosite/MuranoCLIs"
+  rake build &>> ${OUT_FILE} && \
+    gem install -i $(ruby -rubygems -e 'puts Gem.dir') \
+      pkg/MuranoCLI-$(\
+        ruby -e "
+          require \"${projpath}/active+MuranoCLI/lib/MrMurano/version.rb\";
+          puts MrMurano::VERSION
+        "
+      ).gem \
+    &>> ${OUT_FILE} 2>&1 &
+  wait_maybe_fail
+
+  say '' true
+}
+
+lint_it() {
+  lint_it_
+
+  rubocop -D -c .rubocop.yml &>> ${OUT_FILE}
+
+  say '' true
+}
+
+test_it() {
+  test_it_
+# MEH/2017-12-06: The tests take a number of seconds to run, so skipping.
+return
+
+  rake rspec &>> ${OUT_FILE}
+
+  say '' true
+}
+
+ctags_it() {
+  ctags_it_
+
+  local ctags_out=$( { \
+    ctags -R \
+      --exclude=coverage \
+      --exclude=docs \
+      --exclude=pkg \
+      --exclude=report \
+      --verbose=yes \
+    ; \
+  } 2>&1 )
+  if [[ $? -ne 0 ]]; then
+    say
+    say 'ctags FAILED!'
+    say '                                      '
+    say
+    say "${ctags_out}"
+    say
+    say '                                      '
+    say
+  fi
+  /bin/ls -la tags >> "${OUT_FILE}"
+
+  say '' true
+}
+
+wait_maybe_fail_pre_exit() {
+  if ``command -v notify-send >/dev/null 2>&1``; then
+    # 2018-03-12 13:23: Whatever, I cannot test this, why is it so hard to
+    # make the build fail??
+    notify-send \
+      -u critical \
+      -i "${HOME}/.waffle/home/Pictures/Landonb-Bitmoji-Game.Over.png" \
+      'Murano CLI Build Failed!' \
+      "Error: ${wait_for_what}"
+  fi
+}
+
+wait_maybe_fail_success() {
+  if ``command -v notify-send >/dev/null 2>&1``; then
+    #notify-send -i face-wink -t 1234 \
+    #  'Build Success!' 'Murano CLI says, "Woot woot!!"'
+    # 2018-03-19: 1234 msec. is a tad too long. Something quicker,
+    # so I can train myself to ignore if it's a blip in the corner of my eye.
+    # Just make sure your mouse into over popup, or it won't go away!
+    # Hahaha, at 333 msec. it's basically a flash on the screen...
+    #   in that case, there's probably a better way to implement this!
+    notify-send \
+      -t 333 \
+      -u normal \
+      -i '/home/landonb/.waffle/home/Pictures/Landonb-Bitmoji-Thumbs.Up.png' \
+      'Build Success!' \
+      'Murano CLI says, "Woot woot!!"'
+  fi
+}
+wait_maybe_fail_success() {
+  # 2018-03-19 18:04: This just gets better!
+  # sudo apt-get install xcalib
+  ##xcalib -invert -alter
+  #xcalib -alter -invert
+  # xcalib, because of X, only works on the first monitor!
+  # 2018-04-12: But I found a solution that works on all!!
+  /srv/opt/bin/xrandr-invert-colors.bin
+  sleep 0.075
+  ##xcalib -invert -alter
+  #xcalib -alter -invert
+  /srv/opt/bin/xrandr-invert-colors.bin
+}
+

data/.trustme.sh

@@ -1,10 +1,7 @@
 #!/bin/bash
 # vim:tw=0:ts=2:sw=2:et:norl:spell
 
-# WHAT: A Continuous Integration (CI) script for kicking the build
-#       whenever a ruby file within the project is saved.
-#
-#       It's Async-safe!
+# WHAT: A Continuous Integration (CI) script that's async-safe.
 
 # USAGE: If you have Vim, check out the Dubsacks Vim plugin:
 #
@@ -18,73 +15,152 @@
 #
 #          plugin/dubs_edit_juice.vim
 #
-#        Or, if you're not using Vim, wire this shell script
-#        to be called on file save however you are able to
-#        do that.
+#        To wire it yourself instead, check out inotifywait:
+#
+#          https://linux.die.net/man/1/inotifywait
+#
+#        Ubuntu users can install from Aptitude
+#
+#          apt-get install inotify-tools
+#
+#        and then watch files from a shell script, e.g.,
 #
-#          Maybe check out inotifywait:
+#          inotifywait \
+#            -mr \
+#            --timefmt '%d/%m/%y %H:%M' \
+#            --format '%T %w %f %e' \
+#            -e close_write /path/to/project \
+#            | while read date time dir file events; do
+#              /path/to/project/.trustme.sh
+#          done
 #
-#            https://linux.die.net/man/1/inotifywait
+# NOTE:  On Vim, if you're using the project.vim plugin, you'll need
+#        to add a reference to the script from the directory entry.
+#        Otherwise, when you double-click files in the project window
+#        to open them, the BufEnter event doesn't trigger properly.
+#        E.g.,
 #
-# NOTE: On Vim, if you're using the project.vim plugin, you'll need
-#       to add a reference to the script from the directory entry.
-#       Otherwise, when you double-click files in the project window
-#       to open them, the BufEnter event doesn't trigger properly.
-#       E.g.,
+#          MY_PROJ=/path/to/proj in=".trustme.vim" filter=".* *" {
+#            # ...
+#          }
 #
-#         MURANO_CLI=/exo/clients/exosite/MuranoCLIs/active+MuranoCLI filter=".* *" in=".trustme.vim" {
-#           .agignore
-#           # ...
-#         }
+# WATCH: All script output gets writ to a file. Use a terminal to tail it:
 #
-# MONITOR: All script output gets writ to a file. Use a terminal to tail it:
+#          tail -F .trustme.log
 #
-#            tail -F .trustme.log
-
-# MEH: Need to enable errexit?
-#set +x
-
-OUT_FILE=".trustme.log"
-
-#local DONE_FILE=".trustme.done"
-LOCK_DIR=".trustme.lock"
-KILL_DIR=".trustme.kill"
-PID_FILE=".trustme.pid"
-# Hrm. The bang might not work without
-KILL_BIN=".trustme.kill!"
-
-# 2017-10-03: Don't build immediately after every save. If you like to
-# code a little, save, code a little save, repeat, then always running
-# the builder (a) gets annoying to see constantly churning, if you keep
-# a terminal on it; and (b) runs the CPU hot, because eslint. So avoid
-# building too frequently.
-# LATER/2017-10-03: CLI options for this script? It keeps growing!
-# For now, hardcode.
-#BUILD_DELAY_SECS=300
-#BUILD_DELAY_SECS=90
-#BUILD_DELAY_SECS=13
-#BUILD_DELAY_SECS=5
-#BUILD_DELAY_SECS=1
-BUILD_DELAY_SECS=0
-
-# This script is run relative to Vim's working directory, so be deliberate about paths.
-# ${BASH_SOURCE[0]} should be the absolute path to this script.
-TRUSTME_DIR=$(dirname -- "${BASH_SOURCE[0]}")
-OUT_FILE="${TRUSTME_DIR}/${OUT_FILE}"
+# TEST:  From one terminal:
+#
+#          tail -F .trustme.log
+#
+#        From another terminal:
+#
+#          TRUSTME_VERBOSE=true DUBS_TRUST_ME_ON_SAVE=1 ./.trustme.sh
+
+source_plugin() {
+  # This script is run relative to Vim's working directory,
+  # so be deliberate about paths.
+  #   ${BASH_SOURCE[0]} should be the absolute path to this script.
+  # If you add libraries to the trust_me source, source it:
+  #   TRUSTME_DIR=$(dirname $(readlink -f "${BASH_SOURCE[0]}"))
+  #   source "${TRUSTME_DIR}/file"
+  PROJECT_DIR=$(dirname -- "${BASH_SOURCE[0]}")
+  DOTFILENAME=${TRUSTME_BASENAME:-.trustme}
+
+  source_color
+
+  PROJ_PLUGIN="${PROJECT_DIR}/${DOTFILENAME}.plugin"
+  if [[ ! -f "${PROJ_PLUGIN}" ]]; then
+    say "No project plugin! Nothing to do. Hint: Create and edit: ${PROJ_PLUGIN}"
+    exit 1
+  fi
+  source "${PROJ_PLUGIN}"
+}
+
+source_color() {
+  local color_util='color_util.sh'
+  local color_path="${color_util}"
+  # If the /user/home/.fries/lib path is on $PATH, you can just source it.
+  if ! source "${color_path}" &> /dev/null; then
+    # But if it's not on $PATH, see if this script is a symlink, in which
+    # case color_util.sh is also part of this file's owning repo.
+    if [[ -h "${BASH_SOURCE[0]}" ]]; then
+      color_path="$(dirname $(readlink -f ${BASH_SOURCE[0]}))/${color_util}"
+    fi
+    if ! source "${color_path}" &> /dev/null; then
+      >&2 echo "Unable to find and source ${color_util}. You're missing out!"
+    fi
+  fi
+}
+
+assign_globals_() {
+  OUT_FILE="${PROJECT_DIR}/${DOTFILENAME}.log"
+
+  LOCK_DIR="${PROJECT_DIR}/${DOTFILENAME}.lock"
+  KILL_DIR="${PROJECT_DIR}/${DOTFILENAME}.kill"
+  PID_FILE="${PROJECT_DIR}/${DOTFILENAME}.pid"
+  # Hrm. The bang might not work without
+  KILL_BIN="${PROJECT_DIR}/${DOTFILENAME}.kill!"
+
+  # DEVS: You may want to set this, e.g., to 1, or to 300, depending on
+  # how heavy your CI is. If it's a lot of CPU, set a longer delay.
+  BUILD_DELAY_SECS=${TRUSTME_DELAYSECS:-0}
+
+  # FIXME: Add an --arg parser, and add a --verbose/-V flag.
+  TRUSTME_VERBOSE=${TRUSTME_VERBOSE:-false}
+}
+
+assign_globals() {
+  assign_globals_
+}
 
 say() {
-  echo "$1" >> "${OUT_FILE}"
+  FORCE_ECHO=${2:-false}
+  # Restrict newlines to no more than 2 in a row.
+  TRUSTME_SAID_NEWLINE=${TRUSTME_SAID_NEWLINE:-false}
+  if ${FORCE_ECHO} || ! ${TRUSTME_SAID_NEWLINE} || [[ ("$1" != "") ]]; then
+    # Use -e so colors are included.
+    echo -e "$1" >> "${OUT_FILE}"
+  fi
+  if [[ "$1" != "" ]]; then
+    TRUSTME_SAID_NEWLINE=false
+  else
+    TRUSTME_SAID_NEWLINE=true
+  fi
+}
+
+verbose() {
+  ${TRUSTME_VERBOSE} && say "$@"
 }
 
 announcement() {
+  local slugline="$2"
+  local bordelimiter="${3-#}"
+  local hlit="${4-${FG_REG}${BG_MAROON}}"
+  #local hlit="${4-${FG_REG}${BG_MAROON}${FONT_LINE}}"
   say
-  say "###################################################################"
+  local bord=$(repeat_char ${bordelimiter} 67)
+  local norm="${FONT_NORM}"
+  say "${hlit}${bord}${norm}"
   say "$1"
-  say "###################################################################"
-  [[ "$2" != '' ]] && say "$2"
+  say "${hlit}${bord}${norm}"
+  [[ "${slugline}" != '' ]] && say "${slugline}"
   say
 }
 
+verbose_announcement() {
+  ${TRUSTME_VERBOSE} && announcement "$@"
+}
+
+repeat_char() {
+  [[ -z $1 ]] && >&2 echo 'repeat_char: expecting 1st arg: character to repeat' && return 1
+  [[ -z $2 ]] && >&2 echo 'repeat_char: expecting 2nd arg: num. of repetitions' && return 1
+  # Bash expands {1..n} so the command becomes:
+  #   printf '=%.0s' 1 2 3 4 ... 100
+  # Where printf's format is =%.0s which means that it will always
+  # print a single '=' no matter what argument it is given.
+  printf "$1"'%.s' $(eval "echo {1.."$(($2))"}")
+}
+
 death() {
   if [[ -n ${WAIT_PID} ]]; then
     say "Sub-killing ‘${WAIT_PID}’"
@@ -98,14 +174,14 @@ death() {
   exit 1
 }
 
-# FIXME/2017-09-28: Move this and other common fcns. to home-fries?
 lock_kill_die() {
   say "Desperately Seeking Lock on $(date)..."
   [[ "$1" == true ]] && local AFTER_WAIT=true || local AFTER_WAIT=false
   local build_it=false
   # mkdir is atomic. Isn't that nice.
   if $(mkdir "${LOCK_DIR}" 2> /dev/null); then
-    say "Scored the lock!"
+    say "- Scored the lock!"
+    say
     kill_other ${AFTER_WAIT} true
   elif [[ -d "${LOCK_DIR}" ]]; then
     if ! ${AFTER_WAIT}; then
@@ -187,81 +263,95 @@ lock_kill_or_die() {
   lock_kill_die true
 }
 
+# ===
+
+wait_maybe_fail_pre_exit() {
+  : # no-op
+}
+
+wait_maybe_fail_success() {
+  : # no-op
+}
+
+wait_maybe_fail() {
+  WAIT_PID=$!
+  wait ${WAIT_PID}
+  local wait_for_what=$?
+  if [[ ${wait_for_what} -ne 0 ]]; then
+    say "ERROR: See previous error: we sniffed a ${wait_for_what}!"
+    wait_maybe_fail_pre_exit
+    exit ${wait_for_what}
+  fi
+  wait_maybe_fail_success
+  WAIT_PID=
+}
+
 prepare_to_build() {
+  #/bin/rm "${DONE_FILE}"
+  #/bin/rm "${OUT_FILE}"
   rmdir "${KILL_DIR}"
   say
   say "See you on the other side!"
+  say
   touch "${OUT_FILE}"
   truncate -s 0 "${OUT_FILE}"
+  say '' true
+}
+
+# ***
+
+init_it_() {
+  announcement "INIT IT"
 }
 
 init_it() {
-  if [[ -f ${HOME}/.fries/lib/ruby_util.sh ]]; then
-    source ${HOME}/.fries/lib/ruby_util.sh
-  else
-    echo 'Missing ruby_util.sh and chruby' >> ${OUT_FILE}
-    exit 1
-  fi
-  chruby 2.3.3
+  init_it_
 }
 
-lang_it() {
+lang_it_() {
   announcement "LANG IT"
 }
 
-build_it() {
+lang_it() {
+ lang_it_
+}
+
+build_it_() {
   announcement "BUILD IT"
+}
 
-  echo "cwd: $(pwd)" >> ${OUT_FILE}
-  echo "- ruby -v: $(ruby -v)" >> ${OUT_FILE}
-  echo "- rubocop -v: $(rubocop -v)" >> ${OUT_FILE}
-  #echo "- cmd rubocop: $(command -v rubocop)" >> ${OUT_FILE}
+build_it() {
+  build_it_
+}
 
-  local projpath="/exo/clients/exosite/MuranoCLIs"
-  rake build &>> ${OUT_FILE} && \
-      gem install -i $(ruby -rubygems -e 'puts Gem.dir') \
-          pkg/MuranoCLI-$( \
-            ruby -e "require \"${projpath}/active+MuranoCLI/lib/MrMurano/version.rb\"; \
-            puts MrMurano::VERSION"\
-          ).gem \
-      &>> ${OUT_FILE}
+lint_it_() {
+  announcement "LINT IT"
 }
 
 lint_it() {
-  announcement "LINT IT"
-  rubocop -D -c .rubocop.yml &>> ${OUT_FILE}
+  lint_it_
 }
 
-rspec_it() {
-  announcement "RSPEC IT"
-  rake rspec &>> ${OUT_FILE}
+test_it_() {
+  announcement "TEST IT"
 }
 
-ctags_it() {
+test_it() {
+  test_it_
+}
+
+ctags_it_() {
   announcement "CTAGS IT"
-  local ctags_out=$( { \
-    ctags -R \
-      --exclude=coverage \
-      --exclude=docs \
-      --exclude=pkg \
-      --exclude=report \
-      --verbose=yes \
-    ; \
-  } 2>&1 )
-  if [[ $? -ne 0 ]]; then
-    say
-    say 'ctags FAILED!'
-    say '                                      '
-    say
-    say "${ctags_out}"
-    say
-    say '                                      '
-    say
-  fi
-  /bin/ls -la tags >> ${OUT_FILE}
 }
 
+ctags_it() {
+  ctags_it_
+}
+
+# ***
+
 drop_locks() {
+  # FIXME/2017-10-03: Riddle me this: is a two-fer rmdir atomic like a 1 dir?
   rmdir "${LOCK_DIR}" "${KILL_DIR}"
 }
 
@@ -271,11 +361,16 @@ remove_pid_files() {
 }
 
 main() {
+  source_plugin
+
+  # MAYBE: This call is redundant. Do we need to call it again here? Or should we delete first call?
+  assign_globals
+
   # We're called on both save, and on simple buffer enter.
   if [[ ${DUBS_TRUST_ME_ON_SAVE} != 1 ]]; then
     # We've got nothing to do on simple buffer enter...
-    announcement "DUBS_TRUST_ME_ON_FILE: ${DUBS_TRUST_ME_ON_FILE}"
-    say "Nothing to do on open"
+    verbose_announcement "DUBS_TRUST_ME_ON_FILE: ${DUBS_TRUST_ME_ON_FILE}"
+    verbose "Nothing to do on open"
     exit 1
   fi
 
@@ -290,18 +385,17 @@ main() {
   # Get the lock.
   lock_or_die
 
-  say "‘$$’ has the lock"
+  say "- ‘$$’ has the lock"
   echo "$$" > "${PID_FILE}"
   echo "kill -s SIGUSR1 $$" > "${KILL_BIN}"
   chmod 755 "${KILL_BIN}"
 
-  # Always build tags.
+  # Ctags builder. Before the build. In case BUILD_DELAY_SECS is a while.
   ctags_it
 
   announcement "WAITING ON BUILD" "Countdown: ${BUILD_DELAY_SECS} secs..."
 
   # Defer the build!
-  # FIXME/2017-10-03: Riddle me this: is a two-fer rmdir atomic?
   drop_locks
   # The trap on SIGUSR1 only fires when this script is active and
   # not blocked on a subshell. And sleep is it's own command, so we
@@ -315,12 +409,14 @@ main() {
   # Or just wait.
   wait
 
-  say "Ready to build..."
+  say "READY TO BUILD..."
   say
 
   # Get the lock.
   lock_kill_or_die
 
+  say "BUILDING!"
+
   if ${TESTING:-false}; then
     drop_locks
     remove_pid_files
@@ -331,12 +427,12 @@ main() {
   prepare_to_build
 
   time_0=$(date +%s.%N)
-  #say # Put newline after "tail: .rake_build.out: file truncated"
   announcement "WARMING UP"
   say "Build started at $(date '+%Y-%m-%d_%H-%M-%S')"
-  say "cwd: $(pwd)"
+  verbose
+  verbose "- Cwd: $(pwd)"
 
-  #lang_it
+  lang_it
 
   build_it
   function test_concurrency() {
@@ -345,19 +441,23 @@ main() {
   # DEVs: Wanna test CTRL-C more easily by keeping the script alive longer?
   #       Then uncomment this.
   #test_concurrency
+  # A fancy, colorful "Built!" message, meant to be easy to spot.
+  say "${FG_LIME}$(repeat_char '>' 67)${FONT_NORM}"
+  say "${FG_LIME}$(repeat_char '|' 67) BUILT!${FONT_NORM}"
+  say "${FG_LIME}$(repeat_char '<' 67) ${FONT_NORM}"
 
   lint_it
 
-  # MEH/2017-12-06: The tests take a number of seconds to run, so skipping.
-  #test_it
+  # 2017-10-02: I think testing takes too long, and saving often just means constant churn.
+
+  # Unit tests.
+  test_it
 
   time_n=$(date +%s.%N)
   time_elapsed=$(echo "$time_n - $time_0" | bc -l)
   announcement "DONE!"
   say "Build finished at $(date '+%H:%M:%S') on $(date '+%Y-%m-%d') in ${time_elapsed} secs."
 
-  #touch "${DONE_FILE}"
-
   trap - SIGUSR1
 
   remove_pid_files

data/.trustme.vim

@@ -4,6 +4,11 @@
 
 "echomsg "You've been Vimmed! at " . expand('%')
 
+" 2017-11-08: I had wanted to use autocmd, I guess, to have tags
+"   apply to just files within a project, but that's not working so
+"   well -- this plugin might be triggered by BufEnter, so the tags=
+"   wouldn't get set until the user re-enters the buffer...
+
 " @% is same as expand('%'), which for some miraculous reason
 " is the path relative to this file??
 "autocmd BufWrite *.rb echomsg "Hooray! at " . expand('%')
@@ -11,11 +16,12 @@
 
 " Use an autocmd group so it's easy to delete the group,
 " since every time we call autocmd, the command is appended,
-" and this file gets sourced every switch to a corresponding
+" and this file gets sourced on every switch to a corresponding
 " project buffer.
 "augroup trustme
 "  " Remove! all trustme autocommands.
 "  autocmd! trustme
+"
 "  "autocmd BufWrite *.rb silent !touch TOUCH
 "  "autocmd BufWrite <buffer> echom "trustme is hooked!"
 "  " MEH/2017-08-02: This won't hook bin/murano.
@@ -42,8 +48,8 @@ if !exists("g:DUBS_TRUST_ME_ON_SAVE")
 endif
 
 let s:cmd = '!' .
-  \ ' DUBS_TRUST_ME_ON_FILE=' . g:DUBS_TRUST_ME_ON_FILE .
-  \ ' DUBS_TRUST_ME_ON_SAVE=' . g:DUBS_TRUST_ME_ON_SAVE .
+  \ ' DUBS_TRUST_ME_ON_FILE=' . shellescape(g:DUBS_TRUST_ME_ON_FILE) .
+  \ ' DUBS_TRUST_ME_ON_SAVE=' . shellescape(g:DUBS_TRUST_ME_ON_SAVE) .
   \ ' /exo/clients/exosite/exosite-murcli/.trustme.sh &'
 silent exec s:cmd