This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-15
Channels
- # aatree (23)
- # admin-announcements (13)
- # announcements (3)
- # beginners (49)
- # boot (50)
- # braid-chat (1)
- # braveandtrue (37)
- # cider (72)
- # cljs-dev (25)
- # cljsjs (6)
- # cljsrn (37)
- # clojure (78)
- # clojure-berlin (8)
- # clojure-greece (1)
- # clojure-ireland (2)
- # clojure-madison (14)
- # clojure-new-zealand (2)
- # clojure-poland (10)
- # clojure-russia (149)
- # clojured (2)
- # clojurescript (49)
- # community-development (6)
- # core-async (37)
- # cursive (1)
- # data-science (1)
- # datomic (30)
- # emacs (4)
- # euroclojure (1)
- # funcool (1)
- # graclj (1)
- # hoplon (17)
- # jobs (2)
- # jobs-rus (45)
- # ldnclj (6)
- # mount (12)
- # off-topic (124)
- # om (270)
- # onyx (131)
- # parinfer (70)
- # perun (2)
- # proton (168)
- # re-frame (32)
- # reagent (29)
- # ring-swagger (8)
- # testing (9)
- # yada (39)
:thumbsup:
@jessejanderson: I'm trying to merge your pane PR but it doesn't even compile for me
proton handles handlebars beautifying better than spacemacs
@dvcrn: can the errors only show for the given buffer?
@robbyoconnor: need to check that!
[linter.statusIconScope "File"]
should do that. Gonna put that as default for the next release
It's not a biggy
Question: what does it use for beautification?
we started adding https://atom.io/packages/atom-beautify but not sure no the exact state
I use rubocop to format my ruby
just updated my proton install
nucleus is the one of the best themes, because it's adaptive and looks awesome with any syntax theme.
I will send PR. @robbyoconnor did you start to wok on it?
work on what?
@geksilla: I gave up -- i pulled your keymap and keybindings in
for vim-mode
we can use vim-surround
package.
https://atom.io/packages/vim-surround
I dont wanna send a PR -- I'm already spread thin with OSS
contributions
How does it work for vim-mode
as far as I can see that works for vim-mode-plus only... :X
@robbyoconnor, vim-mode-plus enabled by default and has built in support for surround
for vim-mode there is a plugin https://atom.io/packages/vim-surround
so for vim-mode-plus we need to add appropriate key maps to trigger surround actions
ah ok
to me the power of vim is the fact i can copy/paste without using my mouse
I'm not interested in an editor war -- so long as I have modal editing im happy
we need this! https://atom.io/packages/nyancat
typewriter + power-mode + nyan-cat and my coworkers will never take me serious again lol
need to think how to run it properly. We can’t use shadow-build or leiningen (ping @thheller) to collect all the things because of cljs artifacts. I think it would fail right away. I saw that better cljs repl support is coming in the next version though
alternatively, maybe planck for mac can help us with 1-time off scripts (for generation)
For layer and other docs we can just copy all readme files to some directory for released build
nyancat needs to go in the colors
let's model spacemacs
They're doing stuff right
We should slowly aim to match the layers of spacemacs
each layer is exposing keybindings and readme fragments over multimethods. Within proton / cljs we just collect that and generate the prefix tree with that. Now we want to use that information to generate README files. We need a solution to execute all of the cljs code and writes out files
any thoughts on this? I was thinking of just compiling everything down to javascript and load it inside node with calling it’s exposed commonjs functions
each layer’s multimethod is returning a hash (or vector of vectors) that defines the keybindings and settings each layer needs to operate
that information is what we show inside READMEs as well but right now that’s very manual
the part where I was wondering if you have some ideas is how to execute a one off cljs runner that just calls all these multimethods, collects each layers settings and writes out a bunch of README files
is there a way to do this with shadow-build or is the node / browser REPL the only real way to achieving this?
here for example https://github.com/dvcrn/proton/blob/master/src/cljs/proton/layers/lang/ruby/core.cljs#L21-L59
or here for required settings https://github.com/dvcrn/proton/blob/master/src/cljs/proton/layers/lang/ruby/core.cljs#L10-L12
and this is how a readme looks like https://github.com/dvcrn/proton/tree/master/src/cljs/proton/layers/lang/ruby
@thheller: you never saw spacemacs? The fact this is done in clojurescript is kinda epic 😄
@thheller: why not?
Sometimes there's logic that needs to be run
sometimes we need to react on user config and dynamically adjust packages / settings/ etc
the part we want to do next is to collect all of that and spit out readmes for each layer
I bullshitted my elisp for the past 6 months
yes you can use shadow-build to generate a launcher/util for you and node to execute it
I’m not sure how edn deals with anonymous nested functions, for example https://github.com/dvcrn/proton/blob/master/src/cljs/proton/layers/core/keybindings.cljs#L93-L104
but not very useable and you would need to load configs via macros so the correct cljs code can be generated
I had an idea to use bootstrapped repl to compile some parts, like these functions in edn
what is edn
im too lazy to google
@robbyoconnor: clojure is a superset of edn. It's a data notation https://github.com/edn-format/edn
@dvcrn, I'll try to make some demo branch with readme features on top of doc_helper branch.
I think using shadow build to compile a different main namespace and execute that with node might work quite good
@thheller I got one issue when trying to write another atom plugin with shadow-build. Thrown error: 'shadow_umd_helper' already provided