task (gotask) vs task (taskwarrior) - a resolution?

[choman]

I've seen this in the issues page and was looking for a soluion and came up with this

#!/usr/bin/env bash

GOTASK_EXISTS=false
GOTASK_PATH="${HOME}/.local/bin/task"
TASKWARRIOR_EXISTS=false
TASKWARRIOR_PATH="/home/linuxbrew/.linuxbrew/bin/task"

if [[ -x "${GOTASK_PATH}" ]]; then
   GOTASK_EXISTS=true
fi

if [[ -x "${TASKWARRIOR_PATH}" ]]; then
   TASKWARRIOR_EXISTS=true
fi

if ! $GOTASK_EXISTS -a ! $TASKWARRIOR_EXISTS; then
   echo "no task tools exist"
   return 1
fi

if ! $GOTASK_EXISTS || ! $TASKWARRIOR_EXISTS; then
   echo "A task tools exist"
   return 1
fi

export TASK_PATH="${TASKWARRIOR_PATH}"

switch_task() {
  if [[ "$TASK_PATH" == "${GOTASK_PATH}" ]]; then
    export TASK_PATH="${TASKWARRIOR_PATH}"
  else
    export TASK_PATH="${GOTASK_PATH}"
  fi
  echo "Switched to $TASK_PATH"
}

task() {
  bash -c "$TASK_PATH" "$@"
}

NOTE: I'm working an issue with the "bash -c" command

I but this in a file I call 20.functions.task (call it what you want), and source this in my .bashrc.

• It initializes to taskwarrior
• Then tun switch_task to toggle

[trulede]

I would think you could manage this with update-alternatives.

Or just define aliases in your .bashrc file; t => task and tw => taskwarrior.