pkgx: `exec bash` doesn't work.

Per https://github.com/teaxyz/cli#teacli-0222, the correct package should install when I invoke a binary provided by an absent package.

rokejulianlockhart@localhost:~> sh <(curl https://tea.xyz)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 13558  100 13558    0     0  14385      0 --:--:-- --:--:-- --:--:-- 14377
                                        
  hi 👋 let’s set up tea
  
  • we’ll put it here:  /home/rokejulianlockhart/.tea 
  • everything tea installs goes there
  • (we won’t touch anything else)
  
  │ docs https://github.com/teaxyz/cli#getting-started

  k, we installed  /home/rokejulianlockhart/.tea/tea.xyz/v0.22.1/bin/tea 

  
  may we interest you in some magic?
  
  tea’s shell magic is optional but it’s the way it’s meant to be used.
  
  │ docs https://github.com/teaxyz/cli#magic

  Added:
  
   test -d "$HOME/.tea" && source <("$HOME/.tea/tea.xyz/v*/bin/tea" --magic=bash --silent) 

  
  you’re all set!
  
  try it out:
  
   exec bash   # or open a new tab
   wget -qO- tea.xyz/white-paper | glow - 

rokejulianlockhart@localhost:~> krita
If 'krita' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf krita
rokejulianlockhart@localhost:~>

Is whatever provides cnf preventing this, perhaps?

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 15 (8 by maintainers)

Commits related to this issue

Most upvoted comments

@rokejulianlockhart au contraire! The instructions were exec bash I only changed it to exec bash -i due to your bug report! Thank you so much for helping us to correct this.

Well, it doesn’t quite hardcode bash. It does a bit of work to try and figure out exactly which shell you’re running. Using the system default is one of the fallbacks: https://github.com/teaxyz/setup/blob/73a4e8f1ae80a8e0c53bca91d420a7051acefd70/install.sh#L388-L402

Have you started a new shell or otherwise sourced the tea magic?

try it out:
  
   exec bash   # or open a new tab