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
Brothers in Rust, it was brought to my attention that a new user of skim is executing a heathen program written in an inferior language because we lack a printf, observe
In this execution we call out to rg --color=always -n {} $1 interactively. The output of that is in filename:linenumber:linecontents this gets broken up with the glorious argument --delimiter ':' which subsequently gets previewed with an execution of bat {1} -H {2} -f --style=full. Now when sk is given the command to select, there is no ability to the say you only want {1} or {2} or how you want the sk to output. What they're doing is this,
Brothers in Rust, it was brought to my attention that a new user of
skim
is executing a heathen program written in an inferior language because we lack aprintf
, observeIn this execution we call out to
rg --color=always -n {} $1
interactively. The output of that is infilename:linenumber:linecontents
this gets broken up with the glorious argument--delimiter ':'
which subsequently gets previewed with an execution ofbat {1} -H {2} -f --style=full
. Now whensk
is given the command to select, there is no ability to the say you only want{1}
or{2}
or how you want thesk
to output. What they're doing is this,Which offends all of the Gods. It would be far more desirable to support this,
We can even borrow the same logic in
--preview
, and just apply it to the output.The text was updated successfully, but these errors were encountered: