Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't close if default shell quit within a second of starting #364

Open
VarunAgw opened this issue Aug 21, 2016 · 4 comments
Open

Don't close if default shell quit within a second of starting #364

VarunAgw opened this issue Aug 21, 2016 · 4 comments

Comments

@VarunAgw
Copy link

It is very similar to #358 except here shell exists and is closing after giving an error message or just closing.

My default shell is something like c:\cygwin\ssh.exe server. If server is down for some reason, I cannot start Cygwin ever since it close as soon it starts.

Other possible situation (not something that troubles me) maybe some issues in console (cygwin, powershell) configuration. In that case, they will quit with an error message.

@cbucher
Copy link
Owner

cbucher commented Aug 22, 2016

I cannot wait in ConsoleZ during the creation of initial tabs.
If the shell starts, ConsoleZ initialization continue.

I can verify that exit code is not zero (so the shell returns an error).
I can verify that execution is longer than a minimal time.
But what should I do with this information?

@VarunAgw
Copy link
Author

Maybe start a default shell or don't autoclose the tab1 (leaving it inactive)

@rcdmk
Copy link

rcdmk commented Nov 13, 2016

I second this.
In my case I'm having problems with .bash_profile and .bashrc files in Git Bash and this causes my ConsoleZ window to flash on screen and closes in less than a second.

It would be great if the window remain opened so I could read what is going wrong.

If not a desired default behaviour, it can be added as an option for those who desire so.

Thank you.

@VarunAgw
Copy link
Author

VarunAgw commented Nov 13, 2016

Although I have not tested it, but I early read this in change log.

  • Start a safe console when no console started.

Maybe it's done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants