[Rd] cut.default labels when short range

Hello: I stumbled across an anomaly when running cut(4,4) in that the rightmost level's right endpoint did not display the expansion of the range as per ?cut.default. Modifying the last example there cut(0:6, 3) produces the documented behavior, as does cut(0:6, 6) but not cut(0:5, 5) However, cut

[Rd] match.call enhancements in 3.2.2

I was thrilled to see this in the change log: > match.call() gains an envir argument for specifying the environment from > which to retrieve the ... in the call, if any; this environment was wrong (or > at least undesirable) when the definition argument was a function. This was an issue I ran int