clojure-dev

2022-10-31T00:02:21.522269Z

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

Alex Miller (Clojure team) 2022-10-31T01:44:02.216379Z

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.

Alex Miller (Clojure team) 2022-10-31T01:45:13.660559Z

if you want to add Chris Redinger redinger as owner on the repo he's probably the easiest person for me to sync with :)

2022-10-31T01:48:38.369569Z

I have just added redinger as a collaborator on the project. I do not know if that is the same as an owner.

2022-10-31T01:50:14.825589Z

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

Alex Miller (Clojure team) 2022-10-31T01:57:01.117379Z

thx, I'll let him know

seancorfield 2022-10-31T02:24:45.571619Z

Cool to see the cheatsheets getting integrated into http://clojure.org! Thank you!

2022-11-01T19:10:29.989279Z

Looks like the Github repo is transferred to clojure Github org now. Cool!

2022-11-01T19:11:47.494699Z

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.

Alex Miller (Clojure team) 2022-11-01T19:15:34.741519Z

Yeah, I will throw it in a GitHub action probably

Alex Miller (Clojure team) 2022-11-01T19:15:54.395539Z

I started working on recreating parts of the gh pages from your home repo too

👍 1
borkdude 2022-10-31T12:19:10.586949Z

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?

borkdude 2022-10-31T12:20:03.946029Z

Same for flush on newline and print-dup

Alex Miller (Clojure team) 2022-10-31T13:10:34.756349Z

those are declared as dynamic

borkdude 2022-10-31T13:11:57.910269Z

I know, but the metadata doesn't indicate this

borkdude 2022-10-31T13:12:55.702139Z

I ran into this when copying vars into a SCI context based on the metadata (macro true, dynamic true)

Alex Miller (Clojure team) 2022-10-31T13:13:04.339959Z

sure

Alex Miller (Clojure team) 2022-10-31T13:13:47.731219Z

might be different reasons for some of these, like some might be due to deficiencies in defonce (which I think has a ticket)

borkdude 2022-10-31T13:15:24.337809Z

I think it can be fixed by adding a key here: https://github.com/clojure/clojure/blob/master/src/clj/clojure/core.clj#L6537

Alex Miller (Clojure team) 2022-10-31T13:16:04.354699Z

give it a try

👍 1
Alex Miller (Clojure team) 2022-10-31T13:17:07.762099Z

but I'd also want to check if this is really the issue with defonce reevaluation nuking meta

borkdude 2022-10-31T13:22:03.667249Z

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

borkdude 2022-10-31T13:22:21.962739Z

(with the extra key in place in core.clj)

borkdude 2022-10-31T13:31:32.375019Z

I created the issue here: https://clojure.atlassian.net/browse/CLJ-2734 Let me know if a patch is welcome

Alex Miller (Clojure team) 2022-10-31T13:31:45.854099Z

sure thing

borkdude 2022-10-31T13:55:36.475779Z

Patch attached: https://clojure.atlassian.net/browse/CLJ-2734 Assigned to the first of three Alex Millers that popped up :)

2022-10-31T13:55:57.481709Z

I always knew Alex must have clones 🙂

🤯 2
Alex Miller (Clojure team) 2022-10-31T14:07:28.428079Z

the jira transition to Cloud was ... complicated :) resulted in a bit of a clone army which I've given up fixing

4
2022-10-31T14:33:39.791389Z

clone army: bug -> feature

😄 1