Open wwalker opened 5 years ago
Yep, I have very the same problem. I have to run pkill jira
in separate terminal as it locks with every jira
command I have in my script. If I authenticate before running custom command using jira login
then later command works fine.
I never get prompted for a password. and I have to kill the xterm. This is using the custom command:
The child process appears to be prompting for a password but the prompt doesn't show up.
Even blindly pasting in the password and hitting enter doesn't recover.
Maybe before running a child jira, the parent should do authentication?
The real issue here is that it breaks the terminal. If I open a new terminal and kill the jira process, the original terminal is still hosed and needs a
stty sane
Here's what is output to the terminal: