Fork me on GitHub
#off-topic
<
2019-04-30
>
borkdude09:04:04

cljdoc also uses codox

borkdude09:04:29

you could probably run cljdoc locally to see docs of a project.

borkdude09:04:41

there were plans for a Docker image for cljdoc, not sure if that already happened

borkdude09:04:48

ask in #cljdoc for more 🙂

jaihindhreddy11:04:55

Any Pythonistas here, what's your property testing library of choice? (Looking for test.check or quickcheck like library not necessarily spec)

lispyclouds11:04:02

@jaihindhreddy I used https://hypothesis.readthedocs.io/en/latest/ to good effect. Quite pleasant to use too.

👏 4
✅ 8
borkdude15:04:07

what would be a good name for the expressions x y z (bar 1 2 3) in (foo x y z (bar 1 2 3)? I want to come up with a name to skip linting arguments to function calls, so you can say don’t lint arguments to foo.

borkdude15:04:27

the reason is that foo can be a macro which rewrites expressions which gives false positives

borkdude15:04:18

names I’ve already considered: :disable-within, :skip-calls, :skip-args, :not-inside, but it all doesn’t feel satisfying

borkdude15:04:41

note that not the entire (foo ...) expression is skipped, just the linting of the arguments

lispyclouds15:04:21

@borkdude :whitelisted-args or :unchecked-args like *unchecked-math* ?

borkdude15:04:10

then I might prefer :skip-args but keep going 🙂

borkdude15:04:19

what feels wrong to me about args is that (bar 1 2 3) doesn’t feel like an “arg”, but I guess that’s how they call it

lispyclouds15:04:19

im thinking in terms of turn a blind eye towards these args

john15:04:41

elide args?

borkdude15:04:06

:skip-children is more about the AST which would probably be implementation centric

lispyclouds15:04:12

but to the consumer of the API it could be unnecessary impl details?

borkdude15:04:21

which is a bit long in my taste.

borkdude15:04:42

@rahul080327 yes, that’s why I don’t prefer children

lispyclouds15:04:30

somehow I'm more drawn towards names like unsafe { } blocks or native { } wherein we are saying I know what Im doing here hence the use of unchecked IMO

borkdude15:04:36

well, here it’s more like: the linter is almost surely wrong, but you might also still be 😉

borkdude15:04:55

so just skip these parts. skip-args maybe it then

john15:04:21

also :ignore-args

john15:04:53

skip has less characters though

john15:04:15

pretty big factor there

borkdude15:04:25

I already have :skip-comments, so for consistency it may make sense to keep the word skip

borkdude15:04:09

but then again, skip-comments can now be configured yourself as :skip-args [clojure.core/comment], so I’m not sure if that one stays
 🙂

borkdude15:04:03

duckie thanks all

seancorfield17:04:04

(and if anyone genuinely wants to discuss Slack alternatives, we have #community-development for that)

tianshu18:04:50

in linux, how can I know which font is used to display a unicode character icon?

tianshu18:04:39

I think I ran into some issue of the font conflict, but I don't known which font is conflict with the font awesome font(which I used to display icons in status bar)

dkrieger19:04:33

are you on fedora? the packaged font awesome (5, I believe) was known to have this sort of problem. There should be chatter around the issue involving "i3wm" and the like. I was never quite able to solve it and just removed FA icons from my jaybar

tianshu20:04:23

@dougkrieger thanks for the reply. I'm on the manjaro(arch linux), use xfce as desktop.

tianshu20:04:23

I think maybe they are the same. don't know how unicode is displayed. when you install FA, you don't have to use FA as the font, you can use any font but the unicode will be displayed according to the FA.

tianshu20:04:07

now I don't remember what I installed shadow the FA

dkrieger20:04:41

I vaguely remember the issue being some pre-packaged font patched with FA overriding the "real" FA

dkrieger20:04:00

not sure how helpful this is @doglooksgood but there is a command to search fonts by aliases, and if you search "FontAwesome" or the like you might be able to find the culprit (i.e. the alias will resolve to the troublesome patched font)

tianshu20:04:15

so, do you still remember which command?

dkrieger21:04:09

not entirely. the following command should give you some ideas though:

find $(echo $PATH | tr ':' ' ') -name 'fc-*' -exec /bin/sh -c 'echo {} && {} --help && printf "\n"' \;

dkrieger21:04:33

(it's one of the fc-* commands)