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

Close the daemon along with the curses client #3

Closed
langner opened this issue Oct 3, 2012 · 5 comments
Closed

Close the daemon along with the curses client #3

langner opened this issue Oct 3, 2012 · 5 comments

Comments

@langner
Copy link

langner commented Oct 3, 2012

As in the title, is there currently an option to shut down the daemon automatically together with the client?

@themoken
Copy link
Owner

I think you can already achieve this with a keybind:

:bind q remote kill & quit

@langner langner closed this as completed Oct 13, 2012
@langner
Copy link
Author

langner commented Oct 13, 2012

Oh well... I could set it, (and there needs to be a backslash before the ampersand), but it does'nt kill the daemon for some reason. Any idea?

@langner langner reopened this Oct 13, 2012
@themoken
Copy link
Owner

Looks like the message never makes it to the daemon because the connection closes too quickly. I'm not sure if this should be remedied with a wait 5 or something, or if this should be handled externally (i.e. canto-curses && canto-remote kill to invoke canto which does work)

@langner
Copy link
Author

langner commented Oct 21, 2012

Right... I do achieve this currently externally, with this little script:

canto-daemon & canto-curses
kill `jobs -p`

Perhaps using canto-remote kill would be better, though. Maybe you could also add a little boolean option to make sure the daemon is killed before exit?

@themoken
Copy link
Owner

themoken commented Mar 5, 2013

In git I've added

:kill_daemon_on_exit = (True|False)

to enable this functionality.

EDIT: In canto-curses of course

@themoken themoken closed this as completed Mar 5, 2013
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

2 participants