REPL vs CLI: IDE wars

Post by simiones » Thu, Jul 01, 2021, 5:24 PM UTC

marcosdumay wrote: post #26

geokon wrote: post #14

Thanks for introducing me to `add-lib` This is going to be a huge time saver :) More info here: https://insideclojure.org/2018/05/04/add-lib/ Hopefully there will be some way to just "reload" your whole `deps.edn` though "If you get an error, the execution stops by default and you get a stack trace." I'd say the other missing piece of REPL development is that while you get a stack trace, you don't get a program state…

> Maybe I'm "holding it wrong" but this causes a lot of friction and lost time. It is a completely non-problem for functional code. It is a big problem for imperative code. You can't just write all of your code in a functional style, but depending on what you are doing the limit gets larger or smaller. So it's normal that this will be a showstopper for some people, and irrelevant to others.

  compute x = 1 `div` (x - 3)
  map compute [1,2,3,4]

Post by revscat » Thu, Jul 01, 2021, 5:32 PM UTC

a-dub wrote: post #27

protip; you can bring this flow to any language with a repl using vim-slime and a terminal manager like tmux.

Post by fnord77 » Thu, Jul 01, 2021, 5:56 PM UTC

winrid wrote: post #21

smw wrote: post #4

I think you might be missing the main "aha!" of clojure REPLs vs REPLs in non-homoiconic languages: you can very easily execute small parts of the program you're editing without re-typing the code. In emacs, for instance, you often use `eval-last-sexp`, by default bound to C-x C-e. This lets you move your cursor to a particular point in the file, often deep in a function, and get the results of just the form(s) you'r…

You can do this in IDEA's IDEs too, just place a breakpoint and then you can "evaluate expression" in that context to call functions, read values, etc.

Post by thom » Thu, Jul 01, 2021, 6:01 PM UTC

geokon wrote: post #14

Thanks for introducing me to `add-lib` This is going to be a huge time saver :) More info here: https://insideclojure.org/2018/05/04/add-lib/ Hopefully there will be some way to just "reload" your whole `deps.edn` though "If you get an error, the execution stops by default and you get a stack trace." I'd say the other missing piece of REPL development is that while you get a stack trace, you don't get a program state…

Post by aidenn0 » Thu, Jul 01, 2021, 6:05 PM UTC

ajkjk wrote: post #36

godshatter wrote: post #34

> Don’t forget the set -euo pipefail at the beginning of your script. What does -euo means? I don’t know, I copy-pasted it and man set said there is no manual entry for set. Use "man bash" to find the list of built-in commands. Scroll way down, or search for "SHELL BUILTIN COMMANDS". The "e" command-line switch to the set command tells the script to exit immediately if there is a non-zero return value. The "u" switch…

It's kinda nonsense that `man set` doesn't provide that information. But it's kinda nonsense that those flags aren't the default, anyway.

  (set -e; echo hi); echo $?

  if (set -e; false; echo hi); then echo hello; fi

  foo() {
    set -e
    cd /some_directory # set -e means we exit if this fails
    rm -rf *
  }

  cd /some_directory || die "chdir failed"
  rm -rf *