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
Right now \0 refers to the entire match of the regex, which is not necessarily the entire file.
It might be nice to launch sos like so:
sos -p 'hs$' -c 'stack ghc <the-file>'
and have it run stack ghc on any modified file that ends in hs. However, I believe the simplest way to do this (currently) is:
sos -p '.*hs$' -c 'stack ghc \0'
Not too bad, but that extra .* can be annoying. Would it make sense to have magic variable names for the absolute path matched and/or the basename matched?
The text was updated successfully, but these errors were encountered:
Right now
\0
refers to the entire match of the regex, which is not necessarily the entire file.It might be nice to launch
sos
like so:and have it run
stack ghc
on any modified file that ends inhs
. However, I believe the simplest way to do this (currently) is:Not too bad, but that extra
.*
can be annoying. Would it make sense to have magic variable names for the absolute path matched and/or the basename matched?The text was updated successfully, but these errors were encountered: