Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 25 01:41

    brunchboy on master

    Add lunr search to the develope… Update dependencies. (compare)

  • Jan 27 03:57

    brunchboy on master

    Add Sponsor button [skip ci] (compare)

  • Jan 26 06:42

    brunchboy on master

    Need to add sonatype-snapshots … (compare)

  • Jan 26 06:41

    brunchboy on master

    Need to add sonatype-snapshots … (compare)

  • Jan 26 06:36

    brunchboy on master

    Update user guide copyright dat… (compare)

  • Jan 26 06:35

    brunchboy on master

    Update copyright date. (compare)

  • Jan 26 06:34

    brunchboy on master

    Update dependencies. (compare)

  • Jan 26 06:30

    brunchboy on master

    Fix GitHub Actions to upload ja… (compare)

  • Jan 26 06:22

    brunchboy on v0.1.8-SNAPSHOT

    (compare)

  • Jan 26 06:16

    github-actions[bot] on v0.1.8

    (compare)

  • Jan 26 06:15

    brunchboy on master

    Release 0.1.8 (compare)

  • Jan 26 05:56

    brunchboy on master

    Update usb4java version, fix co… (compare)

  • Jan 26 05:17

    brunchboy on master

    Give up on auto deployment atte… (compare)

  • Jan 26 04:47

    brunchboy on master

    Fix maven arguments for deploy … (compare)

  • Jan 26 04:43

    brunchboy on master

    Try setting up automatic Maven … (compare)

  • Jan 25 21:46

    brunchboy on master

    Add automatic module name. (compare)

  • Jan 25 21:39

    github-actions[bot] on v0.1.8-SNAPSHOT

    (compare)

  • Jan 25 21:37

    brunchboy on master

    Try fixing build on GitHub runn… (compare)

  • Jan 25 21:33

    brunchboy on master

    Set up continuous deployment wi… (compare)

  • Dec 28 2019 05:59

    brunchboy on master

    Update change log. (compare)

James Elliott
@brunchboy
Let’s try sending 11 rather than 10 and see if it works.
Would you like to edit the file or have me push the change?
Benjamin Gudehus
@hastebrot
I could edit it if you show me the line number :)
James Elliott
@brunchboy
Line 88 of launchpad_mk2.clj.
Change 24 10 led to 24 11 led.
Benjamin Gudehus
@hastebrot
Done. And now I have to reload my file into the REPL?
James Elliott
@brunchboy
Just that function
(the whole file should be harmless, but if you can find the key for just the function, that is safest)
Benjamin Gudehus
@hastebrot
Hmm, so I just call mk/set-pad-color and it will automatically use the changed source code?
James Elliott
@brunchboy
Correct.
REPL-based development is awesome like that.
(If you have reloaded that function.)
There must be a command in Cursive for that.
Benjamin Gudehus
@hastebrot
Sync files in REPL (Ctrl-Shift-M)
Whoa!
Now it is correct.
James Elliott
@brunchboy
Syncing all the files is way overkill, I still am trying to find how you could have just evaluated that one form, but EXCELLENT.
I will let the person at Novation I am working with about this error in the manual!
How strange that it was doing anything at all with the wrong SysEx prefix.
Benjamin Gudehus
@hastebrot
Loading src/afterglow/controllers/launchpad_mk2.clj... done
Cursive intelligently knows which files were changed.
James Elliott
@brunchboy
The reason I want to do just the function, not the whole file, is that sometimes protocols get redefined, which causes incompatibilities with things that were created before reloading the file.
In this case that did not happen, but in other parts of Afterglow, it does cause issues.
Benjamin Gudehus
@hastebrot
Ahh, ok.
James Elliott
@brunchboy
(It won’t be an issue when you are in your own project.)
Benjamin Gudehus
@hastebrot
Sample cues are also correct.
James Elliott
@brunchboy
That’s great.
Benjamin Gudehus
@hastebrot
(mk2/deactivate mk2-watcher)
CompilerException clojure.lang.ExceptionInfo: Invariant violation in `afterglow.controllers.launchpad-mk2:564` [pred-form, val]:
 [(#{:launchpad-mk2 :launchpad-mk2-watcher} (type controller)), :launchpad-pro] {:*?data* nil, :elidable? true, :dt #inst "2016-02-12T02:08:55.758-00:00", :val :launchpad-pro, :ns-str "afterglow.controllers.launchpad-mk2", :val-type clojure.lang.Keyword, :?err nil, :*assert* true, :?data nil, :?line 564, :form-str "(#{:launchpad-mk2 :launchpad-mk2-watcher} (type controller))"}, compiling:(/home/benjamin/Sources/clojure/afterglow/test/afterglow/afterglow_sample.clj:16:1)
James Elliott
@brunchboy
I can’t see anything after the first line.
Benjamin Gudehus
@hastebrot
Added the rest.
Don't know if this is caused by (def mk2-controller @(:controller mk2-watcher)).
James Elliott
@brunchboy
I am giving up on fighting Cursive to try to figure out how you can run Tools :arrow_forward: REPL :arrow_forward: Run sexp before cursor
That is the command I wanted you to be able to use, but I will leave Cursive support to a Cursive user. I would suggest you explore Edit :arrow_forward: Structural Editing and Navigate :arrow_forward: Structural Movement when you have time.
What does (type c) give you?
Oh, I see!
Yes, my mistake.
Line 686 needs to be {:type :launchpad-mk2})]
Benjamin Gudehus
@hastebrot

Run sexp before cursor

You mean "Send form before caret to REPL"?

James Elliott
@brunchboy
Ah, sounds good! The page I was looking at was outdated.
So if you had put your cursor after the closing paren of set-pad-color and issued that command, it would have redefined just that function for us.
Benjamin Gudehus
@hastebrot
Ahh!
James Elliott
@brunchboy
Do you want to make a pull request with these two fixes, or shall I just do them locally?
Benjamin Gudehus
@hastebrot
I first thought something like (reload 'afterglow.controllers....set-led-color)..
James Elliott
@brunchboy
Ah, I don’t think Clojure itself offers any way of reloading just part of a file like that. But Cursive and CIDER do.
I’m afraid the easiest way to recover from the fact that I gave your controller the wrong type tag is to shut down and reload the REPL after that line is fixed.
Benjamin Gudehus
@hastebrot
I'll make a PR :)
James Elliott
@brunchboy
Great!
Benjamin Gudehus
@hastebrot
Do you have a contributors guideline? Or I'll just put these changes into two commits in a new branch and create the PR.
James Elliott
@brunchboy
Yeah, this is simple and clear. That sounds like a good approach.
I do not yet have contributor guidelines, but we both know what these are about. In the commit messages say something like “correct error in reference manual” for the first, and “correct copy paste error” for the second.