You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, thanks for taking an in interest in this project. For now, I've been treating it as a failed experiment because the code is too buggy for real work and it needs a major rethinking of the way it understands the structure of the code. I haven't had the time needed lately to really iron this out.
In answer to your questions, yes, more sophisticated in either case. Forward-sexp et al, simply count parens (and some other syntactical aspects that emacs is aware of) to find the closing/opening paren. Tactile keeps constant track of the user's position in the code tree and maintains a selection of either an atom or a sexp which the user can manipulate.
The idea here isn't just to give the user some commands to more quickly manipulate plaintext but to let the editor manage the structure of the code. In theory, this would enable a lot of stuff from better mouse interaction much more intelligent auto-completion and code generation. I wrote almost a replacement for a lot of Emacs syntax detection to try to do this.
I have a more complete writeup on my thought process here
Some of the Readme items make me curious.
What is this like?
As in, forward/backward-sexp, or more sophisticated?
As in expand-region and kill-sexp, or more sophisticated?
The text was updated successfully, but these errors were encountered: