Julien Fantin

The last snippet posted by @toupeira is not working for me with the latest version from MELPA. When evaluating the `def-auto-persp` form I get a compilation warning: `Warning: ‘t’ called...

@Bad-ptr Here is the (hairy) backtrace. I suspect it's picking up something in my environment since I've managed to make it work by running @toupeira's config with `(with-temp-buffer (eval '(def-auto-pers...

@Bad-ptr thanks for looking into this, but with version `20160924.308` from MELPA, I'm still getting: ``` Debugger entered--Lisp error: (void-function closure) (closure (t) (_buffer) (if (and (buffer-file-name) (projectile-project-p)) (progn t)))...

@Bad-ptr it does! Thank you.

We have a need for both point 1 & 2 above, and I took a stab at `inject-sub`. @mike-thompson-day8 mentionned on slack that: >To get a general solution, we'd need...

Also took a stab at implementing @mike-thompson-day8 suggestion for point 2. There are a couple of differences here: - The fx accepts a `val->event` fn to generate the event from...

@mike-thompson-day8 interesting, that does look simpler too. I also had some comments about a potential issue if the sub that's injected is never used in a component. If that assumption...

Thanks for the review @mike-thompson-day8 It seems a good compromise would be to have the co-fx log a warning if it disposes of an injected sub. If the cache miss...

We shipped the [inject](https://github.com/vimsical/re-frame-utils/blob/master/src/vimsical/re_frame/cofx/inject.cljc) cofx in a pre-release of our [re-frame-utils](https://github.com/vimsical/re-frame-utils). People following this issue might want to check it out!

@vikeri cool! Docs are still on the todo list, but the [fx handler for inject](https://github.com/vimsical/re-frame-utils/blob/master/src/vimsical/re_frame/cofx/inject.cljc#L32) has a decent docstring showing usage example as well as some behavior notes that you...