Skip to content
This repository has been archived by the owner on Jul 9, 2019. It is now read-only.

Add 'minimum time between self-updates' option #60

Closed
thorinii opened this issue Mar 23, 2015 · 6 comments
Closed

Add 'minimum time between self-updates' option #60

thorinii opened this issue Mar 23, 2015 · 6 comments

Comments

@thorinii
Copy link

When developing, Halcyon checks for updates reasonably often. It'd be nice if there was an option to let it take longer between checking; an hour or so would do. Or every day.

If this happens, Halcyon will probably need another option to force checking, just in case I need that latest update you just pushed.

@thorinii
Copy link
Author

In an empty, non-project directory, running time halcyon build for the first time takes 6.2 seconds. The second time takes 0.3.

@mietek
Copy link
Owner

mietek commented Mar 23, 2015

I agree. The self-update grace period is currently just 1 minute, and should be increased.

@pbrisbin has suggested that self-updating should be disabled by default. I agree with the reasoning, but I’m not sure if I’ll be able to provide support without the assumption that everyone is running master.

@thorinii
Copy link
Author

I think auto-update should be on by default (particularly for the automated builds) -- you've already got an option to turn them off globally. A self-update grace period option would just make it better.

@AKurilin
Copy link

I use tmux very heavily and every time I open a new pane after the 60 seconds timeout, I have a 2-5 sec delay because of the halcyon update. Is this the same issue reported here? Any reason this check can't be significantly more infrequent, maybe 60 mins?

@mietek
Copy link
Owner

mietek commented May 24, 2015

@AKurilin: Yes, the self-update grace period should be increased. Meanwhile, you can change your ~/.bash_profile to disable self-updates:

eval "$( HALCYON_NO_SELF_UPDATE=1 /app/halcyon/halcyon paths )"

In the future, this line will no longer be automatically added to ~/.bash_profile (#46 (comment)).

@mietek
Copy link
Owner

mietek commented Feb 14, 2019

I’m sorry. This project is no longer maintained.

@mietek mietek closed this as completed Feb 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants