[Bug 4175] New: revision sets should accept UPPERCASE keywords

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Tue Feb 18 19:08:36 CST 2014


          Priority: normal
            Bug ID: 4175
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: revision sets should accept UPPERCASE keywords
          Severity: feature
    Classification: Unclassified
                OS: All
          Reporter: gregory.szorc at gmail.com
          Hardware: All
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

I was teaching somebody about revision sets. I had them type in a boolean
query. They typed an uppercase "AND". To my surprise, Mercurial choked with a
not very friendly error message:

$ hg log -r "ancestors(.) AND author('gps at mozilla.com')"
hg: parse error at 13: invalid token

Changing the "AND" to "and" made the error go away.

I think the revision set parser should accept uppercase variants of the known

There's also room to improve the error message - perhaps by providing some
context. But that's another issue.

Please let me know if we should do this and I'll code it up.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Mercurial-devel mailing list