This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-22
Channels
- # aws-lambda (2)
- # beginners (195)
- # boot (47)
- # capetown (14)
- # cljs-dev (7)
- # cljsjs (1)
- # cljsrn (1)
- # clojure (103)
- # clojure-berlin (28)
- # clojure-dev (92)
- # clojure-dusseldorf (3)
- # clojure-finland (2)
- # clojure-germany (3)
- # clojure-italy (4)
- # clojure-russia (37)
- # clojure-spec (104)
- # clojure-uk (52)
- # clojured (2)
- # clojurescript (124)
- # community-development (7)
- # core-async (6)
- # cursive (41)
- # datomic (53)
- # dirac (2)
- # emacs (16)
- # hoplon (5)
- # jobs (3)
- # juxt (12)
- # lein-figwheel (6)
- # leiningen (15)
- # luminus (3)
- # off-topic (49)
- # om (5)
- # onyx (13)
- # overtone (27)
- # re-frame (7)
- # reagent (46)
- # ring (3)
- # ring-swagger (11)
- # spacemacs (2)
- # specter (40)
- # sql (6)
- # untangled (149)
- # vim (14)
in lispy/lispyville, if I'm in the middle of a string, say "foo|" then when I press ", what I wnat: "foo"| what I get: "foo\"|\"" how do I tell lispy -- when I hit ", I wnat to exit string -- I don't want to insert a quote dstring ?
Hey folks, I use Emacs and my colleague uses Cursive (sorry!) - works fine but there's a few differences in the way indentation works between the two that's a pain! Is there a way to get Cursive to use the same indentation style as Emacs and apply it automatically?
@eggsyntax thanks for reminding me to follow up on that issue. I came up with a fix but didn't submit it as a PR yet. I was hoping to get some more feedback on it since I'm not sure how good of a fix it is, but I'll open a PR that might be a quicker way to get feedback
@plexus I saw that, thanks for figuring that out! It seemed like a reasonable solution to me, at least for now. Let's get that puppy into master 😉
In the meanwhile if anyone has a clue about what inf-clojure provides that inf-lisp doesn't I'm all ears. I've been telling people "it's better because it's Clojure specific" but no idea what that actually implies.
the only thing I can think of is that it knows about metadata and reader forms so it sends things as ^:foo [:bar]
or #.foo.Bar [:baz]
as a single form
is anyone running into gc issues with emacs? it seems that someitmes, after an emacs session has been running for 2-3 days, it starts becoming laggy for ABSOLUTELY NO REASON -- i.e. when I'm ediitng an org snippet that is < 100 lines long
I don't know if it's (1) an org mode special edit thing (2) a lispy thing [unlikely, as editing plain *.cljs files tend to not lag] or (3) a emacs-has-been-running-too-long thing
@qqq I generally leave my emacs (in server/daemon mode) running in the background on my linux machine for weeks at a time without noticing any speed differences. Similar to my OSX expectations (except in the order of days instead of weeks as an average run time)