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

Calling zeal twice without a query parameter should raise the window instead of doing nothing #187

Closed
edgimar opened this issue Aug 6, 2014 · 4 comments
Assignees
Milestone

Comments

@edgimar
Copy link

edgimar commented Aug 6, 2014

When running zeal more than once without a query parameter, one gets the message "Already running. Terminating." and then the program exits. It would be better if it would trigger the already-running instance to raise itself if it is hidden. If there's a problem with making this the default behavior, then at least there should be an additional commandline option which does this.

@amclain
Copy link

amclain commented Aug 7, 2014

I second this. I ran into an issue where there was no way in the GUI to restore Zeal after hiding it. It's also helpful for those of us who spend a lot of time in the command prompt. Having the window restore after executing the zeal command would be convenient.

@RossBarnie
Copy link

+1 Got this now and can't seem to bring up zeal at all even after killing the original process. Probably a separate bug.

@amclain
Copy link

amclain commented Aug 23, 2014

@RossBarnie I figured out the workaround for that problem is to open up the Zeal config file (~/.config/Zeal/Zeal.conf) and change the following parameters:

hidingBehavior=minimize
startupBehavior=window

Then if you restart the process, the window should come back up. Unfortunately it looks like setting both the hiding and startup behavior to system tray causes the window to be hidden permanently. This is also referenced in issue #128.

@trollixx trollixx added this to the 0.1.0 milestone Jan 10, 2015
@trollixx trollixx self-assigned this Jan 10, 2015
@lock
Copy link

lock bot commented Sep 16, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.

@lock lock bot locked and limited conversation to collaborators Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

4 participants