-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse pipe-composition of commands #5
Comments
Oh crap, search terms. This may require more thought … |
Yeah, search terms are going to be annoying. There's also Here are the composite commands I can find in my .tridactylrc:
|
Awesome! I was planning to come ask y'all for a corpus of example commands 🤣 For bind, I can't believe I haven't written it down anywhere, but I guess I was quietly assuming we'd support parenthetical disambiguation of expressions of some form! For example:
|
Oh, and I explicitly, strongly, very very very strongly do not want to try to support complicated usages of I'm sure we can add some interim heuristics on the |
This needs discussion, though I haven't thought about it in detail yet. Obviously the existing hack using
composite
can be done away with entirely. Less-obviously, I think we aren't going to see any of the problems that Vim's excmds have with the pipe — i.e. needing to conditionally support pipe-as-composition with some commands, but not others?Thoughts and feedback welcome. Probably going to throw together naive,
command | another_command
support pretty soon; and can develop edge-cases from there.This is one place where good examples of real-world uses of
composite
would be great.The text was updated successfully, but these errors were encountered: