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
We'd like to be able to say "bring air before bat", "move air after bat", etc, rather than "bring air to before bat", "move air to after bat", etc.
I wonder if we also want to support "move after bat" as shorthand for "move this to after bat". Note that this behaviour won't come for free with the above change, because saying "move after bat" is actually supported today, but it doesn't do what you might expect: it will take the empty range after the "bat" token and insert it at the current position. So I believe it will be equivalent to "chuck this"! Haven't test that hypothesis tho 😊
We might consider being stricter about where user can use positional modifiers like "after" and "before", because you can / will be able to recover their functionality more naturally in other ways, so maybe they should just be allowed in specific places. For example
"take air past before bat" => "take air till bat"
"move air to before bat" => "move air before bat"
"take before bat" => "pre bat"
"take line before bat" will use the special construct "<SCOPE_TYPE> before"
"move this before bat" => "move before bat"
Not sure bout the last paragraph; just a thought. Could be useful to have fully compositional positional modifiers
The text was updated successfully, but these errors were encountered:
pokey
transferred this issue from cursorless-dev/cursorless-talon
Jan 12, 2022
We'd like to be able to say "bring air before bat", "move air after bat", etc, rather than "bring air to before bat", "move air to after bat", etc.
I wonder if we also want to support "move after bat" as shorthand for "move this to after bat". Note that this behaviour won't come for free with the above change, because saying "move after bat" is actually supported today, but it doesn't do what you might expect: it will take the empty range after the
"bat"
token and insert it at the current position. So I believe it will be equivalent to "chuck this"! Haven't test that hypothesis tho 😊We might consider being stricter about where user can use positional modifiers like "after" and "before", because you can / will be able to recover their functionality more naturally in other ways, so maybe they should just be allowed in specific places. For example
"<SCOPE_TYPE> before"
Not sure bout the last paragraph; just a thought. Could be useful to have fully compositional positional modifiers
The text was updated successfully, but these errors were encountered: