Fork me on GitHub
#cursive
<
2017-08-02
>
wilkerlucio00:08:39

@cfleming I'm trying to find a way to automatically have (s/instrument) to run when I change my files, so in dev time I have the functions always instrumented, ideas?

wilkerlucio11:08:29

@U0D5RN0S1 thanks, that's a cool trick 🙂 what I have done is change my "Load current file on REPL..." keymap, now instead I'm using a REPL command that runs (s/instrument) and load the current file, so now every time I reload a file I get the instrumentation 🙂

cfleming00:08:18

@wilkerlucio Hmm, I can’t think of a better way to do that than an explicit REPL command.

wilkerlucio03:08:34

@cfleming I'm wondering if there is something I can hook up at REPL level, do you know if there is any trigger for file loaded there that I could hook on?

cfleming03:08:26

@wilkerlucio The thing is, you’ll have to run an action of some sort anyway to load your code in the REPL, right?

cfleming03:08:52

So couldn’t you create a REPL command for (s/instrument) which syncs your files?

wilkerlucio03:08:22

humm, I guess you right, the only issue is see here is that my need for (s/instrument) is project dependent, so can be a bit annoying to keep changing the keymap,

wilkerlucio03:08:24

but maybe I can just make the command safe to run when spec is not available, I'll give a shot, thanks for the suggestion 🙂

pelletier20:08:00

@cfleming feature suggestion: a button in the REPL panel that stops the REPL and starts it again.

bfabry22:08:28

lol... I would use that more often than I'd care to admit