On Sat, Jan 27, 2018 at 10:17 AM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Check with Trevor - in Levure he waits for a signal on a port that ST sends
> when there is a save and then magically reloads.
The way the Levure/SublimeText integration works is as follows:
oooh. I didn't think of doing that with git...
On Sun, Jan 28, 2018 at 6:13 PM, Monte Goulding via use-livecode <
use-livecode@lists.runrev.com> wrote:
> It’s always going to be safest to close LiveCode, checkout a different
> branch and then reopen LiveCode but just like people setup stuff so
It’s always going to be safest to close LiveCode, checkout a different branch
and then reopen LiveCode but just like people setup stuff so they can use
external code editors you could add a git hook that notified the IDE that the
worktree had changed and to reload things.
> On 27 Jan 2018, at
Check with Trevor - in Levure he waits for a signal on a port that ST sends
when there is a save and then magically reloads.
On Fri, Jan 26, 2018 at 3:29 PM, Geoff Canyon via use-livecode <
use-livecode@lists.runrev.com> wrote:
> With version control, switching branches switches out SoS files.
With version control, switching branches switches out SoS files. Is it
best/necessary to then run through the stackfiles and set the destroystack of
each to true and close/reopen them? Or is there a better way?
gc
___
use-livecode mailing list
