This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-06
Channels
- # adventofcode (24)
- # aleph (1)
- # bangalore-clj (2)
- # beginners (196)
- # boot (148)
- # cider (18)
- # clara (83)
- # cljsrn (24)
- # clojure (210)
- # clojure-brasil (3)
- # clojure-china (1)
- # clojure-italy (11)
- # clojure-korea (8)
- # clojure-russia (82)
- # clojure-spec (115)
- # clojure-uk (130)
- # clojurescript (109)
- # core-async (7)
- # cryogen (1)
- # cursive (22)
- # datascript (11)
- # datomic (6)
- # devcards (2)
- # emacs (1)
- # garden (1)
- # hoplon (2)
- # incanter (1)
- # klipse (4)
- # luminus (4)
- # off-topic (89)
- # om (53)
- # onyx (78)
- # parinfer (9)
- # proton (3)
- # protorepl (20)
- # re-frame (107)
- # reagent (52)
- # rum (30)
- # spacemacs (1)
- # testing (3)
- # untangled (31)
- # vim (43)
- # yada (9)
General Unix question: I have a command that returns something, e.g. a filename, on stdout. What I'd like to have is a way to refer to that text, usually the last line of output, without moving the mouse.
Has anyone found a way to do that? Ideally without re-running the command.
hmm yeah, although that does re-run the command
my use case is that i run something interactively, and only then realize that I may need the output
sort-of like *1
in the clojure repl
I'm using zsh, so open to zsh-based solutions!
any pointers?
http://unix.stackexchange.com/questions/117054/can-zsh-access-the-stdout-of-last-run-program
for bash and zsh, AFAIK, the answer to your question is there is no equivalent of *1 in clojure repl
pesterhazy : is it something you could solve with judicious use of pipes/xargs/etc instead?
if its the same command you could alias the command to export SOME_VARIABLE=$(command | tail -1)
@hunter, yes I probably could
but it would just be so damn useful to be able to refer to the script's output without copy'npasta
it's the shell's blind spot
ok, bash/zsh have many many blind spots, but it's one of them
Well, given that stdout is a file. You could probably firehose it into a file. And read it back later.
@dexter perhaps the terminal emulator would be the best place to get this
http://unix.stackexchange.com/a/14732 this seems promising
don't use eshell and would prefer not to
http://unix.stackexchange.com/a/323920 automatic starting of script in bash 😄
things you would never see @clojureconj .. https://twitter.com/AngeBassa/status/805011667289604096
was there an article in there? I know they are trying to go more mainstream and focus on articles
it could be cover to cover with articles about distributed computing and quantum physics, it still objectifies women on the cover. Also, playboy will always have a reputation no matter what they try to focus on. Try keeping a playboy on your desk at work and explaining to your boss that it's all about the articles now.
https://erikbern.com/2016/12/05/the-half-life-of-code.html was a pretty interesting exploration of how long source code tends to survive in various projects
I ran the code against clojure and got this:
Largely as I expected; clojure code tends not to go away. But there’s an odd discontinuity at 2014. Anyone know what they might reflect?
I was thinking maybe transducers
@gdeer81 i wasn't trying to justify an obviously bad choice. I was just wondering if there was some motivation that I wasn't aware of
@dpsutton whatever the intent they didn't think about the impact. Nothing screams "boyz club" like a stack of mags
@donaldball I was about to go to lunch before you posted that, now I'm sitting here pouring through the clojure commit history in 2014 while my tummy is rumbling lol
ha ha sorry
something big happened though: https://github.com/clojure/clojure/graphs/code-frequency
It looks like almost all of the drop was circa 2007 code going away (that’s the only bar that got smaller, the others just shifted as a result)
Not sure what was done in 2007 that went away in 2014, though
From the blog post, it looks like the stats are based on git blame; so it could have been somebody just moving a folder tree
ha, that seems a likely explanation
I assume it was changing our internal asm version
We dropped the old one and added the new one
Probably the biggest delta I ever committed
It’s… instructive to contrast with the rails graph: https://raw.githubusercontent.com/erikbern/git-of-theseus/master/pics/git-rails.png
Different projects with different use cases to be sure
mostly additive
the asm version change is the only case I can recall where I straight up deleted a big wad of code and replaced it
gdeer81 I doubt it :)
yeah some were mundane like updating doc strings and whatnot, but there are some interesting commits in there 😃
anyone go to the conj?
wooooo awesome 😄
how does it compare to just watching the videos online?
the videos are excellent. the incredibly nice and brilliant people you meet at an alex miller conference are what really makes it
outstanding. Was really hoping to catch the datomic pre-conference workshop but alas 😄
@gdeer81 maybe we should just pre-record the talks, play them in an empty room, and hang out in the hall
hahaha!
@alexmiller I was referring to the discussions between talks and on breaks, but yeah I did meet people that said they miss most of the talks and just talk to people in the halls
Really need to go to EuroClojure next year had such a blast 2 years ago