Clojurians Log v2

Hi is there any alternative to the pgUp pgDown shortcut?

also I can't seem to find it mentioned in the docs

@stuartmitchell: https://github.com/binaryage/dirac/issues/9

hello 😄

I am finally trying to get a working dirac env 😄

of course using boot and boot-cljs-devtools

thanks Darwin, everything is very well documented!

sooo one thing, I am clicking on the extension icon but nothing happens, what can it be?

the extension icon should display some exclamation symbol or question mark symbol, hovering over the icon should display some reason

also some message should be present in javascript console

Nothing of that, the agent is hooked I think and everything seems OK, let me try again

in case dirac devtools window is already opened for given page, clicking on the icon just focuses it and does nothing else

oh ok then

I am also adding a patch to boot-cljs-devtools so I might be doing something wrong there too

yeah VM859:1 Unable to resolve backend-url for Dirac DevTools. target-url=<http://localhost:8000>, tab-url=<http://localhost:8000/>

it looks like I am missing something

likely you are not running your chrome with enabled debugging port or wrong debugging port

target-url is wrong, it should be something like http://localhost:9222, I guess you were messing with dirac extension options and changed that default

yes that was it, now can I call (dirac.runtime/install!) from anywhere?

“target url for debugger” is url for DevTools to connect to, at this URL your chrome remote debugger protocol should be available, I should probably explain more on the options screen

you should call runtime/install! in your app, preferably as early as possible

ideally before any of your own code runs

I see Installing Dirac Runtime v0.2.0 and enabling features :repl

but (+ 1 3) fails

Uncaught SyntaxError: Unexpected number(…)

ah so so sorry, I copied the dep from a place but it was very old, I apologize for the noise

you are probably not entering the command into cljs REPL but in plain javascript consolel

use PAGEUP to switch prompt types

ah wow didn't know that

perfect now it does work!

the documentation is not that good after all 🙂

I have to improve this, you are not the first one hitting this problem

maybe just add a "baby steps" section...the rest was very clear

patch is working than: https://github.com/jupl/boot-cljs-devtools/pull/3

I don’t think it is a good idea to repeat those defaults, when I decide to change them for some reason you will be stuck with previous

yeah true I can actually just refer to your var

just refer to this file: https://github.com/binaryage/dirac/blob/master/src/agent/dirac/agent/config.clj and fill only config options which are explicitly specified by the user

done neat!

hmm, shouldn’t you call get-effective-config instead of default-config?

you want to test effective dirac agent port against your nrepl port

there are two problems with current version: a) you should not be using default-config at all, just specify only options you want to override, dirac will fall back to defaults for others

b) in that assert you want to merge get-effective-config with your dirac-opts overrides and check the port

because some settings could come from ENV properties and override defaults

oh, good that you checked

I did not even know that you could configure it from ENV var

https://github.com/binaryage/dirac/blob/master/docs/configuration.md

ok ,so no defaults at all in there and I will use get-effective-config for the assert only

ping me with updated code and I will check

tnx

not yet ready 😄

@darwin basically get-effective-config is not "right" until I pass my config to boot!

therefore I cannot assert there with it right?

the assert is more on my side I guess

assuming envrionment is constant, it will be right if you pass in your dirac-opts as parameter, it will merge defaults, environ and your config

https://github.com/binaryage/dirac/blob/master/src/agent/dirac/agent/config.clj#L34

this is what boot! does: https://github.com/binaryage/dirac/blob/master/src/agent/dirac/agent_impl.clj#L135

ok the patch should be ok, the assert is just to check that we have not bugs and the user does not include inconsistent option to repl and dirac

as it is written currently the assert should never fail

yeah

over-engineering and against bugs I guess

but i'll leave it there

The task works like a charm now! I will include it (optionally) in https://github.com/Lambda-X/lambone

@richiardiandrea: cool! thanks for your care