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
I'm using autotype for typing, which supports both stdin and the first argument selection.
The workaround is to let bemoji echo output and pipe it to the tool, but that defeats the whole point of supporting custom typing tooling selection that's built in:
$ bemoji -ne | autotype
The text was updated successfully, but these errors were encountered:
Previously, stdin contents were consumed and then not passed through to
the typing tool. With this commit, they are correctly passed to any
custom tool's stdin.
Fixes#19.
Previously, stdin contents were consumed and then not passed through to
the typing tool. With this commit, they are correctly passed to any
custom tool's stdin.
Fixes#19.
We are passing the selection contents through to any custom typing (or clipping) tools through stdin.
However, for custom typing tools specifically, stdin was consumed but not propagated to the tools.
I'm confused about how custom typing tool selection is supposed to work at https://github.com/marty-oehme/bemoji/blob/main/bemoji#L171.
I'm using autotype for typing, which supports both stdin and the first argument selection.
The workaround is to let bemoji echo output and pipe it to the tool, but that defeats the whole point of supporting custom typing tooling selection that's built in:
The text was updated successfully, but these errors were encountered: