This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-31
Channels
- # aleph (12)
- # announcements (4)
- # asami (7)
- # babashka (20)
- # beginners (92)
- # calva (74)
- # clj-kondo (8)
- # cljdoc (70)
- # clojure (47)
- # clojure-dev (29)
- # clojure-europe (27)
- # clojure-nl (7)
- # clojure-norway (3)
- # clojurescript (7)
- # cursive (2)
- # datomic (1)
- # emacs (8)
- # events (5)
- # fulcro (36)
- # gratitude (4)
- # humbleui (25)
- # introduce-yourself (1)
- # lsp (26)
- # malli (6)
- # missionary (8)
- # nbb (50)
- # off-topic (9)
- # pathom (2)
- # pedestal (3)
- # portal (32)
- # practicalli (5)
- # reitit (5)
- # releases (1)
- # ring (6)
- # shadow-cljs (87)
- # sql (31)
- # tools-deps (26)
- # vim (3)
- # xtdb (15)
No rush on my part, but if what I have done so far for resolving this issue on transferring the clojure-cheatsheets repo under the Clojure Github organization is not sufficient, happy to try something else: https://github.com/jafingerhut/clojure-cheatsheets/issues/50
yeah, it's in my list - I think what needs to happen is for you to make someone that is a clojure org owner the owner and then they can transfer it. I am not an owner, but I haven't had a chance to sync up with any of the other folks yet.
if you want to add Chris Redinger redinger
as owner on the repo he's probably the easiest person for me to sync with :)
I have just added redinger as a collaborator on the project. I do not know if that is the same as an owner.
Ah, I just found the option to transfer the ownership of the repo to another user id. I attempted to transfer it to redinger, and it says it is in the process of being transferred
thx, I'll let him know
Cool to see the cheatsheets getting integrated into http://clojure.org! Thank you!
Looks like the Github repo is transferred to clojure Github org now. Cool!
I suspect that if others want to update and regenerate the cheatsheet in the future, you might prefer different ways to automate it than are currently checked in. I'm happy to answer questions about anything there that is confusing, or walk someone through my steps and make sure they are all written in some README file in that repo somewhere.
Yeah, I will throw it in a GitHub action probably
I started working on recreating parts of the gh pages from your home repo too
Found that *print-readably*
doesn't have :dynamic
set on the metadata:
user=> (:dynamic (meta #'clojure.core/*print-readably*))
nil
Want a ticket/patch for that?those are declared as dynamic
I ran into this when copying vars into a SCI context based on the metadata (macro true, dynamic true)
might be different reasons for some of these, like some might be due to deficiencies in defonce (which I think has a ticket)
I think it can be fixed by adding a key here: https://github.com/clojure/clojure/blob/master/src/clj/clojure/core.clj#L6537
but I'd also want to check if this is really the issue with defonce reevaluation nuking meta
This works:
clj -Sdeps '{:deps {org.clojure/clojure {:local/root "target/clojure-1.12.0-master-SNAPSHOT.jar"}}}'
Clojure 1.12.0-master-SNAPSHOT
user=> (:dynamic (meta #'*print-dup*))
true
I created the issue here: https://clojure.atlassian.net/browse/CLJ-2734 Let me know if a patch is welcome
sure thing
Patch attached: https://clojure.atlassian.net/browse/CLJ-2734 Assigned to the first of three Alex Millers that popped up :)
the jira transition to Cloud was ... complicated :) resulted in a bit of a clone army which I've given up fixing