This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-05
Channels
- # beginners (23)
- # boot (84)
- # braid-chat (2)
- # bristol-clojurians (1)
- # cider (53)
- # cljs-dev (34)
- # cljsrn (13)
- # clojure (138)
- # clojure-dusseldorf (5)
- # clojure-italy (1)
- # clojure-russia (164)
- # clojure-uk (41)
- # clojurescript (80)
- # clr (2)
- # core-async (6)
- # core-logic (25)
- # core-matrix (14)
- # cursive (10)
- # data-science (4)
- # datomic (4)
- # emacs (3)
- # funcool (6)
- # hoplon (127)
- # jobs-discuss (4)
- # keechma (36)
- # ldnclj (5)
- # lein-figwheel (5)
- # off-topic (5)
- # om (155)
- # onyx (72)
- # overtone (16)
- # parinfer (39)
- # planck (3)
- # protorepl (1)
- # re-frame (11)
- # reagent (5)
- # untangled (22)
Yeah, I agree, I think that’s going to be the change that will allow some people to use it at work who can’t currently.
right, I think that’s what all non-inferenced modes would converge to
What I’m worried about is how slurping and barfing will work without tons of commands.
lispy has that down
I mean, obviously you can’t map normal insertion/change events to those operations
This has actually been a great change in terms of figuring out how to handle all these things in IntelliJ - turns out I can easily hook things like delete line and tidy up the parens, which I didn’t realise.
it uses the vim-like hjkl
keys to make it quick
Right, but it’s very context-sensitive. I can imagine it being powerful but it’s not newbie-friendly.
right, that’s the caveat
my hope is that the auto-mode and the parinfer-criticism can be realized as full thing
So I’ll need to go through and look at things like evil-cleverparens and see what to steal. They have some nice heuristics for fixing up pasted code which is something I’ve wanted to do for ages.
and for us to be able to compare tradeoffs
yeah, I think Cursive would be perfect grounds to explore that
Yeah, we definitely need a full implementation to see one against the other. What he discussed in that doc was a hodge-podge of existing modes, which even for an existing Emacs user is probably unrealistic.
but for Cursive...
And I’m excited to be able to remove the distinction between the modes and just compose the features as required.
cool, thanks for all the context. chat with you soon, good luck
@shaunlebron: Oh, one more question
With the tab stops change, I calculate the tab stops and if the user hits tab but their code is already at or past the last stop, I just indent two spaces.
I’m wondering if that is ever useful, or if it would be better to just not do anything.
ah, good point to bring up, yeah
nah, I think falling back on normal indenting is good
for example, for aligning a two-line comment
would be annoying to not be able to push the cursor to a certain point after a tab stop
so yeah, I think your idea is good behavior, two-spaces
published 1.8.0 with the new tabStops
feature
added tests and docs. changes are split by commit to make for easier porting: https://github.com/shaunlebron/parinfer/pull/110/commits
tab stops are not used in the demo editor yet
@cfleming: something I’ve had in mind since the beginning is allowing space
and shift
+`space` to indent/dedent selected lines by a single space. This would the user the ability to correct an off-by-one alignment caused by the usual two-space jumps
@shaunlebron: Right, something like that would be required in the auto-indent case, for sure.