How can I use .bash_profile aliases in black-screen?

[Krystus]

Why I can't use .bash_profile aliases in black-screen? I have to do something or it is impossible for now?

[vlad-shatskyi]

They should be imported automatically. If they're not, it's a bug, and I'd need more information about your setup.

[Krystus]

@shockone I have a test release 0.36.4 on iMac 27" El Capitan 10.11.3 (15D21).

[vlad-shatskyi]

In Black Screen, press cmd+option+i to open developer tools, switch to the Console tab and type process.env.SHELL is it /bin/bash?

If yes, please try to copy the file .bash_profile to .bashrc and reload Black Screen.

Please let me know if any of this helped.

[Krystus]

Yes, that was /bin/bash. After .bash_profile to .bashrc copy of aliases easy commands like desk, twc working. But take a look at my aliases in second screen... homestead up and twc.start/stop still don't work at all. command "function" not found and php-fpm.start: command not found.

[vlad-shatskyi]

There are three bugs. Good catch!

• Aliases aren't expanded after command separators (&&, |). That's why php-fpm.start does't work. Should be fixed soon.
• .bash_profile isn't loaded. It's intended for non-interactive sessions, but clearly people use it as interactive session configs too. Should be fixed soon.
• Shell's built-in functions don't work. In your case function, but also things like nocorrect and so on. Might be harder to fix.

[vlad-shatskyi]

Now you don't need .bashrc.

[ilanbiala]

Have these three issues been fixed?

[vlad-shatskyi]

Only the second one at the moment, @ilanbiala.

[eliorc]

I'm having the same problem with Ubuntu 18.04, Upterm 0.4.3.

All my aliases are in ~/.bashrc and are not being loaded - meaning they don't work and obviously don't autocomplete.

Typing process.env.SHELL in the developer tools console shows /bin/bash

[zautumnz]

Is this related to builtin problems in #1215?