4 ms·
I'd love to understand your point of view a bit more. What do you mean by "context sensitivity"? Symex isn't context-sensitive in general and operates much like
by countvajhula 5y ago
I'd love to understand your point of view a bit more. What do you mean by "context sensitivity"? Symex isn't context-sensitive in general and operates much like Vim/Evil in terms of consistency (e.g. you can define repeatable macros). Are you thinking of Lispy, which makes heavy use of context (and is certainly clever)? Re: the commands being second nature, that is very much a goal, and if there's something that could be better here for holdouts like yourself, I'd love to understand what that might be.
- b3morales 5y agoNot the original commenter, but I think I know what they were getting at. Basically a given command may do something "different" with regard to the bare text, depending on the start position in an S-exp. For example, in these two (where | is point) (foo bar |baz) vs. (foo bar |baz) moving "up", point will end up on the same line in the first and two lines up in the second. This, of course, is the point of structured editing, but it takes a bit of getting used to I think, and at first commands can seem sort of "unpredictable" or, as said "context sensitive" in a way that's different from more basic movement. (Though comparable to something like M-a for prose, of course.)