On Wed, Mar 30, 2011 at 11:53:45PM -0700, Jason Gerecke wrote:
> On Wed, Mar 30, 2011 at 8:57 PM, Peter Hutterer
> wrote:
> > On Wed, Mar 30, 2011 at 01:54:41PM -0700, Jason Gerecke wrote:
> >> For many commands, improper arguments cause a silent failure. The
> >> user is often given no indication
On Wed, Mar 30, 2011 at 8:57 PM, Peter Hutterer
wrote:
> On Wed, Mar 30, 2011 at 01:54:41PM -0700, Jason Gerecke wrote:
>> For many commands, improper arguments cause a silent failure. The
>> user is often given no indication if their command succeeded or
>> failed. I've tried to find all the sile
On Wed, Mar 30, 2011 at 01:54:41PM -0700, Jason Gerecke wrote:
> For many commands, improper arguments cause a silent failure. The
> user is often given no indication if their command succeeded or
> failed. I've tried to find all the silent "return;" statements and
> provide some kind of warning me
For many commands, improper arguments cause a silent failure. The
user is often given no indication if their command succeeded or
failed. I've tried to find all the silent "return;" statements and
provide some kind of warning message where possible.
In some cases I've added in new checks to ensure
