I like the feature sending path to the bound destination so much, that I want to add a variation that sends to the active terminal.
How to integrate this without creating confusion ? I do not want to spin off a different extension for a power-user feature like this. Should I keep the RangeLink: prefix to avoid potential confusion and add the contextual menu items in a different section ?
Or we somehow transform/brand RangeLink into a "we provide so many productivity feature" extension ? (I like this less because our focus must remain on precision when integrating with various AI assistants)
The same power features/keybindings targeting the bound destination could all get a "to Active Terminal" variation: is it really a good idea to add those options ? Perhaps gate them behind a preferences (which would be off by default) ?
I like the feature sending path to the bound destination so much, that I want to add a variation that sends to the active terminal.
How to integrate this without creating confusion ? I do not want to spin off a different extension for a power-user feature like this. Should I keep the
RangeLink:prefix to avoid potential confusion and add the contextual menu items in a different section ?Or we somehow transform/brand RangeLink into a "we provide so many productivity feature" extension ? (I like this less because our focus must remain on precision when integrating with various AI assistants)
The same power features/keybindings targeting the bound destination could all get a "to Active Terminal" variation: is it really a good idea to add those options ? Perhaps gate them behind a preferences (which would be off by default) ?