This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-06
Channels
- # bangalore-clj (16)
- # beginners (120)
- # boot (21)
- # cider (24)
- # clara (9)
- # cljs-experience (1)
- # cljsrn (1)
- # clojure (218)
- # clojure-dev (3)
- # clojure-italy (12)
- # clojure-losangeles (4)
- # clojure-norway (2)
- # clojure-russia (2)
- # clojure-spec (19)
- # clojure-uk (178)
- # clojurescript (52)
- # cursive (7)
- # data-science (55)
- # datomic (25)
- # defnpodcast (11)
- # emacs (5)
- # fulcro (27)
- # hoplon (2)
- # leiningen (14)
- # midje (9)
- # off-topic (132)
- # onyx (19)
- # other-languages (23)
- # portkey (2)
- # re-frame (31)
- # reagent (1)
- # ring-swagger (15)
- # shadow-cljs (58)
- # slack-help (13)
- # spacemacs (22)
- # sql (7)
- # test-check (13)
@dromar56 I use CIDER for getting in-buffer evaluation of Clojure code. Once I'm jacked in (`cider-jack-in`/`C-c M-j`) I just eval at point with eval-last-sexp
/`C-x C-e`.
Anyone know the solution for this? When I invoke Amazon aws
cli under eshell
any “help” output (`aws help`, aws lambda help
, etc) does not get intercepted into a buffer like the output of man
or less
, even though under the hood the cli appears to implement paging with less -R
. As a result
$ aws help
WARNING: terminal is not fully functional
- (press RETURN)
@gonewest818 maybe rlwrap/readline issue, memory is blurry
I’m RTFMing right now … eshell-visual-commands
and eshell-visual-subcommands
found it. (setq eshell-visual-options '(("aws" "help")))