GBT__CONF undefined when using gbt_sudo

[jtyr]

GBT__CONF undefined when using gbt_sudo

[rgcv]

True, but I guess that isn't the case when using sudo. I'll get to submitting a PR ASAP!

[jtyr]

Thanks for opening this issue. Please can you share what OS and shell you are using and show your configuration for setting up GBT in your shell config file?

[rgcv]

Sure thing! Currently using bash, here's the relevant portion of my rc file:

case "$(tty)" in
  /dev/tty*) ;;
  *)
    if command -v gbt &>/dev/null; then
      PS1='$(gbt $?)'
      export GBT__HOME="/usr/share/gbt"
      source "$GBT__HOME/sources/gbts/cmd/local.sh"
      # skipping mysql, su, and sudo, look broken
      for c in docker screen ssh vagrant; do
        alias $c=gbt_$c
      done; unset c
    fi
    ;;
esac

EDIT: Happens with zsh as well, pretty sure it's shell independent?

I'm running Arch Linux x86 64-bit.

Linux ge62vr-6rf 5.0.10-arch1-1-ARCH #1 SMP PREEMPT Sat Apr 27 20:06:45 UTC 2019 x86_64 GNU/Linux

Also, I'm not aliasing mysql because, for some reason, the cursor ends up at the rightmost column, only wrapping after typing a few characters, but that's another issue.

EDIT 2: (unrelated) Found another issue in gbt_finish using zsh, outputs error: garbage option when called. I'll open proper issues soon after further testing a bit, possibly.

[jtyr]

The GBT__CONF is defined during the transfer of the scripts to the remote machine. After you ssh to a remote machine, you should be able to find the value of that variable by running this command:

echo $GBT__CONF

That should print the location of the script (/tmp/.gbt.<NUM>).

Please can you test if the variable is defined right after you ssh somewhere? If it is, check that the variable is also exported on the top of the /tmp/.gbt.<NUM> file.

[jtyr]

The MySQL issue is known. The MySQL client has some differences across versions and interprets unicode characters incorrectly if you connect to MySQL DB of version X with MySQL client of version Y.

[rgcv]

Please can you test if the variable is defined right after you ssh somewhere? If it is, check that the variable is also exported on the top of the /tmp/.gbt.<NUM> file.

Loud and clear. It appears the variable is set remotely, and the first line of the file indeed includes the export line:

export GBT__CONF='/tmp/.gbt.<NUM>'

The MySQL issue is known. The MySQL client has some differences across versions and interprets unicode characters incorrectly if you connect to MySQL DB of version X with MySQL client of version Y.

I would expect that, yes, it makes sense. However, I just tested on my own box, where client and server obviously match, and I still observe the same exact behavior.. which beffudles me 😕

[jtyr]

If the GBT__CONF is defined then using rm -f $GBT__CONF $GBT__CONF.bash should be just fine. But you are right, the removal of the files should be inside the else branch of the condition. Would you like to create PR for that?