You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In PR #1298 , some shell integration scripts have been added so the terminal's title would change according to the program running. As a downside, a source command and a clear command would been shown every time a new terminal has been created (refer to the screenshot below). We have to find a way to have these things running somewhere where the user can't see them.
The current source command have a downside, which is it have to be run in the current shell process, so, if we don't hide the terminal outputs while it's running, it just have to be shown to the user.
On the other hand, the script like what iTerm is using can be run anywhere because it's detecting if the user's source file (~/.zshrc, etc.) contains the right integration script, and if they don't, add the source command to those file, so this script can be executed in any terminal (we can create a terminal without a view for that), and our shell integration scripts would always be loaded even there's no extra commands executed in that exact shell. But we'll have to write something in user's shell's source file. (We chose not to do this when implementing #1298 , but I think it's the best solution that I can come up with for now.)
Screenshots
The text was updated successfully, but these errors were encountered:
Description
In PR #1298 , some shell integration scripts have been added so the terminal's title would change according to the program running. As a downside, a
source
command and aclear
command would been shown every time a new terminal has been created (refer to the screenshot below). We have to find a way to have these things running somewhere where the user can't see them.Alternatives Considered
No response
Additional Context
I'm already looking into this problem:
The current idea is to add another install script like what iTerm is using.
The current
source
command have a downside, which is it have to be run in the current shell process, so, if we don't hide the terminal outputs while it's running, it just have to be shown to the user.On the other hand, the script like what iTerm is using can be run anywhere because it's detecting if the user's source file (
~/.zshrc
, etc.) contains the right integration script, and if they don't, add thesource
command to those file, so this script can be executed in any terminal (we can create a terminal without a view for that), and our shell integration scripts would always be loaded even there's no extra commands executed in that exact shell. But we'll have to write something in user's shell's source file. (We chose not to do this when implementing #1298 , but I think it's the best solution that I can come up with for now.)Screenshots
The text was updated successfully, but these errors were encountered: