This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (2)
- # beginners (97)
- # boot (3)
- # cider (23)
- # clara (9)
- # cljs-dev (40)
- # cljsrn (6)
- # clojure (107)
- # clojure-finland (2)
- # clojure-india (3)
- # clojure-italy (15)
- # clojure-nl (2)
- # clojure-spec (107)
- # clojure-uk (91)
- # clojurescript (28)
- # cursive (10)
- # data-science (4)
- # datomic (26)
- # duct (1)
- # emacs (6)
- # events (9)
- # figwheel-main (4)
- # fulcro (4)
- # graphql (2)
- # jobs (3)
- # jobs-discuss (12)
- # juxt (7)
- # kaocha (6)
- # off-topic (8)
- # onyx (2)
- # parinfer (13)
- # pedestal (32)
- # portkey (1)
- # re-frame (58)
- # reagent (17)
- # reitit (21)
- # ring-swagger (3)
- # shadow-cljs (35)
- # spacemacs (1)
- # tools-deps (33)
- # yada (13)
@slipset Dang, in ClojureScript, you can get away with
(keyword nil :user/foo); my friend Hyrum showed me this.
It be nice if instead of using
rebel-readline. That would prevent the need for having rlwrap separately installed, and would just be in general a superior readline experience
I know you can do it with an Alias. Just saying, if you're going to depend on another tool with a different license, why not depend on a rebel-readline as default instead
One which clojure can pull on its own at that, so it doesn't even have to be installed
It's been discussed. There just aren't the right hooks to enable it right now, as I recall the discussion...
Hum, interesting. Wonder what can be missing, since you can right now start it given an alias.
@seancorfield I've been looking at extending clj-new.generate. make the defn able to handle specifying args, docs, body, etc. generate yaml and some other stuff. Do you think it could grow, or should I be looking somewhere else?
Hum, or I guess rebel readline does need to bootsrap itself with its own main class, and maybe kicks off its own repl. Anyways, hopefully it could eventually be leveraged.
To be the first thing you get when you first try Clojure, it would be pretty impressive
@jwhitlark I'm still here. It's early here in CA 🙂 I'm open to PRs on that, for all sorts of stuff.
Vivesh Siddharthipor and Vikram Banerjee seem to be bots - they joined the channel together - should be blocked. (Update: they have updated their names and profile pics by coping other users name and pics)
Looks like some coordinated (human or bot) time-waste attack goin on here - New person Shekhar just joined
I'm muting this channel until an Admin has this under control. Imho we shouldn't give these people any more attention by answering or anything.
Blocked one user but it’s a little hard tracking users down. If you can provide they exact usernames please send me a DM
may I suggest limiting
at-everyone, I think its relatively easy to limit who can use it when
@UDF11HLKC I looked into this but either my permissions (workspace admin vs. owner) are lacking or those docs are outdated. I asked a workspace owner to take a look as well.
@martinklepsch There are some abusive messages with “everyone” marked by “Ajay” and “munen” handles (timestamp 12.55PM onward) - please delete when you get time.
Would be more accurate to reference them by their member id instead of their handle.
Just woke up to see the remains of the chaos from while I was asleep. FWIW @-everyone can only be used by Admins and Workspace Owners, as can @-channel and @-here -- regular members should not be able to use them.
I think they're only blocked by the UI, not by the API itself. That means a bot can bypass it.
I think Slack has taken a firm stance that you should trust your employees, which doesn't really apply to us.
Weird, since it is admin/owner-only in the settings. Well, sorry for all the inconvenience. We are definitely "short" in terms of Admin coverage for that period of time (late Pacific through until early Europe time). We need at least one Asian or Antipodean Admin added.
Thank you @U8MJBRSR5 -- I'll let the Admin team know you're willing and you and I can chat about what's involved later today (the start of your day).
Hey all, Currently I am trying to deploy a repo to a private maven repository. I am having an issue figuring out how to reference a environmental variable in the project.clj of the project. I have tried the 3 following methods but have had no success. Side Note: I am using a Windows operating system
I am currently defining the environment variable via the cmd.exe with windows. When I use
~(System/getenv "foo") I get the following error...
`WARNING: please set :description in project.clj.
WARNING: please set :url in project.clj.
No credentials found for snapshots(did you mean
lein deploy clojars?)
lein help deploying for how to configure credentials to avoid prompts.
It seems as though it's not even checking my environment variables
I’m sure this has been talked about before on here, but does anyone have any opinions about having predicates that return true or nil?
My personal preference is that any function that ends with
? returns a boolean, but if it doesn't then I'm fine with truth-y or false-y return values
I’d be surprised and slightly annoyed if
foo? returned anything other than a boolean
if you have something that can return true, false or nil it might make more sense to return keywords that describe what’s happening instead
(that doesn't actually work because false / nil don't work in set-as-spec but anything else would ruin the joke) fixed
I wouldn’t loose much sleep over using
nil/`false` interchangeably in a predicate, but I would nerd rage over a non-boolean truthy value. straight booleans would be preferred