This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (9)
- # announcements (5)
- # babashka (3)
- # beginners (46)
- # calva (21)
- # cider (15)
- # clj-kondo (20)
- # cljs-dev (57)
- # cljsrn (10)
- # clojure (147)
- # clojure-dev (6)
- # clojure-europe (3)
- # clojure-france (2)
- # clojure-italy (8)
- # clojure-nl (18)
- # clojure-norway (5)
- # clojure-spec (16)
- # clojure-uk (63)
- # clojuredesign-podcast (7)
- # clojurescript (65)
- # clojurex (42)
- # crux (3)
- # cursive (12)
- # datomic (10)
- # fulcro (47)
- # graalvm (102)
- # graphql (2)
- # jobs (5)
- # joker (12)
- # off-topic (33)
- # pedestal (6)
- # re-frame (6)
- # reagent (8)
- # reitit (6)
- # remote-jobs (4)
- # rewrite-clj (10)
- # shadow-cljs (86)
- # sql (45)
- # testing (4)
- # tools-deps (43)
- # vim (8)
Java lib author asking how he can make his lib more Clojure friendly: https://twitter.com/picocli/status/1192612734619115521?s=20
String docstring = "Usage: prog [options]\n\nOptions:\n-h, --help Print help."; AbstractMap<String, Object> result = clj.docopt(docstring, args);
When making a comparison table, do you differentiate properties of the construct vs properties of the artifact, e.g. storing in namespace means singleton.
hey, ace table (for anyone lacking context: https://clojurians.slack.com/archives/C06MAR553/p1573217468113700?thread_ts=1573136280.098800&cid=C06MAR553)! kudos. I don't understand the question. I think those are terms which exact intent I forgot ;p
I'm often confused when people use the word transparent. Does it mean "easy to perceive" or "invisible"?
In this context it means that it is invisible to someone. In this case, it is invisible to the start/stop concept that async is happening
I'm inclined to avoid the word invisible as it has magical connotations. What I'm referring to is the same as the ability for you to layer caching into an existing thing, without that thing having to make everything aware of caching
Automatic could be a better word? I fear abstraction would imply I'd created my own async abstraction, which I've not.
It's possible there's no perfect way to describe the "transparent"/"invisible" stuff - look at literature on aspect-oriented programming, they have to invent their own jargon to get the point across
I have a bash script I wrote that contains about half dozen commands that are run via
sudo, and many more that are not run via
sudo, and I would like only the ones with
sudo to run as root. That all works as desired, except that the script is fairly long running (about an hour), and if more than 15 minutes or so pass between two
sudo commands, the later
sudo again prompts the user for their password. Does anyone know a way to enable the user entering their password once, regardless of the timing?
The script is only intended to work on Ubuntu Linux, so I'm fine with methods specific to that, if it makes it any easier.
Run the whole thing as root and use sudo to switch to the non-priviledged user for non-root commands (`sudo -u <normaluser> <command>`)
Hmm. I hadn't thought of that approach. It will be a lot of
sudo -u <normaluser> commands, but yeah, seems workable.
@jkr.sw Your approach is mostly working, but I had not anticipated that some of the commands in my script are invoking other bash scripts, which use sudo to elevate privileges inside of them... Ugh.
I can make patches to those scripts that edit them in similar ways as the top level script, but it is getting tedious.