--explain for preferred/required content matching
And annex.largefiles and annex.addunlocked. Also git-annex matchexpression --explain explains why its input expression matches or fails to match. When there is no limit, avoid explaining why the lack of limit matches. This is also done when no preferred content expression is set, although in a few cases it defaults to a non-empty matcher, which will be explained. Sponsored-by: Dartmouth College's DANDI project
This commit is contained in:
parent
ba1c222912
commit
518a51a8a0
12 changed files with 89 additions and 60 deletions
|
@ -76,6 +76,8 @@ getUserInfo :: MonadIO m => UserInfo a -> m a
|
|||
getUserInfo (Right i) = return i
|
||||
getUserInfo (Left e) = liftIO e
|
||||
|
||||
newtype MatcherDesc = MatcherDesc String
|
||||
|
||||
type FileMatcherMap a = M.Map UUID (FileMatcher a)
|
||||
|
||||
type MkLimit a = String -> Either String (MatchFiles a)
|
||||
|
@ -97,7 +99,7 @@ data MatchFiles a = MatchFiles
|
|||
-- ^ displayed to the user to describe whether it matched or not
|
||||
}
|
||||
|
||||
type FileMatcher a = Matcher (MatchFiles a)
|
||||
type FileMatcher a = (Matcher (MatchFiles a), MatcherDesc)
|
||||
|
||||
-- This is a matcher that can have tokens added to it while it's being
|
||||
-- built, and once complete is compiled to an unchangeable matcher.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue