https://bz.mercurial-scm.org/show_bug.cgi?id=5517
Bug ID: 5517
Summary: `hg blame doesntexist exists` doesn't eagerly error
out
Product: Mercurial
Version: default branch
Hardware: PC
OS: Mac OS
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: duri...@gmail.com
CC: mercurial-devel@mercurial-scm.org
This confuses git users. We should probably check all the filenames before
doing any blaming, and if any filename doesn't exist abort right away, so that
git users get an error message that makes sense instead of seeing blame at a
revision they don't expect. That is:
$ hg blame deadbeef README
today prints the blame of `README` at ., then aborts because `deadbeef` isn't a
file. A git user expects that to blame `README` at revision `deadbeef`, and if
pager is on they probably don't even see the abort, which stinks.
We could even try and offer up a hint that if something looks rev-like that
maybe they want -r. I'm not sure we can sneak a "git compat" mode in for blame
here though, feels a little risky (but I'm open to being convinced on that
front).
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
