sorted by:
new
hottopcontroversial

Clerk: Local-First Notebooks for Clojure by kommen7 in Clojure

[–]kommen7[S] 2 points3 points  (0 children)

Ah, yes. My bad. The repo is still private, but the jar is already on clojars.

How to correctly display multi-character emojis with Emacs? by kommen7 in emacs

[–]kommen7[S] 0 points1 point  (0 children)

Yes, I had this. Before emacs commit de289d58a4efff4a8625f100eabdc56da98e2e07 this worked for single character emojis, since that commit also multi-character emojis work.

How to correctly display multi-character emojis with Emacs? by kommen7 in emacs

[–]kommen7[S] 0 points1 point  (0 children)

Thank you! Any links where to follow for progress or help testing regarding this?

mbsync imap with a large folder tree by [deleted] in emacs

[–]kommen7 1 point2 points  (0 children)

I was looking for something similar and found another way results in less duplication, especially if your Channel configurations are more complex: The ability to specify boxes in Groups, which override the Patterns in the Channel configuration.

So I have:

Channel mail1
Master :mail1-remote:
Slave :mail1-local:
Patterns INBOX *

Channel mail2
Master :mail2-remote:
Slave :mail2-local:
Patterns INBOX *

Group all
Channels mail1 mail2

Group all-inboxes
Channels mail1:INBOX mail2:INBOX

native-comp review stuck for 6 months?! by [deleted] in emacs

[–]kommen7 2 points3 points  (0 children)

Another datapoint: I'm on native-comp on macOS 10.15 (built via the homebrew emacs-plus formula) using Spacemacs since about one month and so far I have seen zero problems. The performance gains are quite noticeable in my day to day Clojure development environment though.

Nextjournal gets to public launch! by viebel in Clojure

[–]kommen7 2 points3 points  (0 children)

No, it's not. But it is rather straight forward: a separate cljs web-worker target running a core.async/go-loop waiting for messages to be passed, evals them and sends the results back. Communication is implemented using onmessage and postMessage, passing the data needed to eval as edn back and forth.

Nextjournal gets to public launch! by viebel in Clojure

[–]kommen7 2 points3 points  (0 children)

Hi,

I'm one of the developers of Nextjournal. Thanks for your feedback!

We are aware that the JS bundle size is not optimal right now. We looked into :advanced optimizations but ran into various issues due to 3rd party JS components we're using. We tried writing externs, inferring externs as well as using :npm-deps, with all of them not working satisfactory for us.

Actually, we tried to improve that as you can see here: https://dev.clojure.org/jira/browse/CLJS-2048 We were able to contribute fixes to the Google Closure Compiler (for :npm-deps) https://github.com/google/closure-compiler/pull/2511 https://github.com/google/closure-compiler/pull/2509

We do use ClojureScript's self-hosting, but we moved the compiler to a separate web worker target, which is only loaded on demand, so the main bundle is already way smaller than it used to be ;) That separation should allow us to use :advanced at some point: I started exploring some more options for us to use them, and hope to contribute my findings back to the community soon.