This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-27
Channels
- # aleph (8)
- # announcements (14)
- # beginners (25)
- # cider (20)
- # cljdoc (5)
- # clojure (70)
- # clojure-europe (2)
- # clojure-germany (6)
- # clojure-italy (8)
- # clojure-nl (3)
- # clojure-russia (107)
- # clojure-spec (22)
- # clojure-uk (40)
- # clojurescript (18)
- # core-async (3)
- # cursive (8)
- # data-science (11)
- # datomic (20)
- # editors (1)
- # emacs (5)
- # figwheel-main (19)
- # fulcro (25)
- # graphql (1)
- # hoplon (2)
- # hyperfiddle (2)
- # jobs (1)
- # leiningen (3)
- # lumo (4)
- # off-topic (40)
- # pedestal (1)
- # quil (4)
- # re-frame (5)
- # shadow-cljs (105)
- # sql (4)
- # uncomplicate (1)
Morning morning
https://github.com/todotxt/todo.txt anyone remember this?
I'm trying Orgzly. My only meh is that it's hiding the text at the top of the file. But that might be normal for org files.
Oh, and also that Orgzly doesn't work with sub-folders. I had intended to use org as a wiki. So I would have files like "pokemon/squirtle.org" and "work/death_star.org", things like that.
I've started using C-u C-x C-e
in rich comment blocks to start to build up unit tests. I'm reasonably happy with it but feel I could build something with some more sugar potentially (tho it is a good workflow for now)
@U0JUM502E yeah, C-x C-e
is eval-last-sexp
and the C-u modifier inserts it. IIRC it works in most lisp-ish modes the way you'd expect.
@otfrom I do something similar. I've been using comment
forms for some time, usually below functions to "evolve" the code for the function as I'm developing it and sometimes those turn into things that are worth putting into formal "unit tests". I felt validated when I heard Stu refer them as Rich Comment Forms (because that's what Rich does).
I was doing that too and thought I was "cheating" until I heard that Rich and Stu do it. I think the only problem I have is that b/c I'm usually parsing some clients data I tend to leak too much client info into the things I'm writing (which can be a problem if they are FLOSS π )
putting C-u
in front of the C-x C-e
to capture what I want for testing I've only started doing, well, today
Write a spec
and generate
random data for it? π
@seancorfield I should do. π
What does C-u C-x C-e
do different to just C-x C-e
? (it's been years since I used Emacs now)
I think we've talked about this before though, and it is just a pain to write the generators when creating strings that parse to int/double/date/etc
putting the C-u means that it ends up in the buffer you are editing rather than in the minibuffer echo
@otfrom Ah, yeah, we have our own set of generators for that, built via macros from predicates and stringify functions.
I'd still love to find a library that does nice string -> type conversions. It is getting dull re-writing them all the time.
Hmm, "evaluate into the buffer". I hadn't thought of that as a key-bound workflow. Useful. I should propose it as an addition to Chlorine π
We should open source some of our string -> type conforming specs and generators I suppose.
I finally created a GitHub organization for work so we can publish stuff more easily!
Once we have a few more things up there, we'll probably publicize it https://github.com/worldsingles -- the commons
repo has our condp->
and similar macros.
@dominicm @otfrom Obviously I am using Spacemacs to write most of the content in .org files, I am using Github to share my orgfiles these days as they render pretty well (will be looking at tweaking some of the css GitHub uses - would be cool if the headings folded like in Emacs). I use orgly on Android for taking notes when I donβt want to break out the laptop. I just sync those notes with Dropbox and then add them to Github when back on the laptop.