Mykola Gurov
Mykola Gurov
Same issue here. I can see it even when comparing the pdf rendering for the [second page](https://revealjs.com/#/1) of the standard reveal.js demo. The arrow images at the ["vertical slides"](https://revealjs.com/#/2) section...
proof of the concept implementation available @ https://github.com/mgurov/Gitifier/tree/noClonesButInlineFetchingForLocal
From my personal experience, neither of the points appeared to be a problem. - when doing `get fetch`/`git pull` manually, you clearly see the updates and then there are no...
Looking into the code, the sync is based on `git fetch` which doesn't give a range of revisions for new branches: ```2012-04-09 13:46:07.140 Gitifier[2769:307] running command git fetch ( )...
https://github.com/sickill/git-dude/blob/master/git-dude has a handling logic for a similar problem
proof of the concept implementation available @ https://github.com/mgurov/Gitifier/tree/newBranchTracking
The cause of this issue is that the `.Listen()` doesn't make copy of the `Progress.closeChan`, and misses the moment when it is replaced by `nil` at `.Stop()`.
A simple, albeit imperfect workaround is to remove the bars from the progress: ``` go progress.Bars = nil ``` it is still not perfect as there will be one more...
Simplest solution would be to make a copy of the stop chan and use `time.Ticker` instead of `time.Sleep`: ``` go func (p *Progress) Listen() { p.lw.Out = p.Out stopChan :=...