[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Suggestion: "svn explain"

From: mark benedetto king <bking_at_inquira.com>
Date: 2002-08-05 20:44:00 CEST

I'm replying to the wrong message, since I deleted the right one.
Apologies in advance.

On Mon, Aug 05, 2002 at 02:30:59PM -0400, Greg Hudson wrote:
> On Mon, 2002-08-05 at 14:07, Dave Cridland wrote:
> > As mentioned before, Google is often the best source of online help for
> > what errors *really* mean.

I'm not always connected to the internet. I like to code in airports
and on planes. In fact, that's usually my only opportunity to code because
when I'm online I'm buried in AIM messages and e-mails.

The "svn help" suggestion is very similar to Oracle's "oerr" facility.

Oracle gives you error "1469", and you are welcome to type

$ oerr ora 1469
01469, 00000, "PRIOR can only be followed by a column name"
// *Cause: Attempting to specify "PRIOR <something>" where <something> is not
// a column name.
// *Action: Only a column name can follow PRIOR. Replace with a column name.

> > Since the rest of the string can be internationlised, I for one would
> > really like a "This is error code 'SVNERROR_TOOMANYERRORCODES'" string
> > somewhere, giving me a suitable searchable token.

These could be locale-specific strings.

Sure, google might take you to the Discussion Group For People Who
Get Error Message Number 1469, but *something* local for problem resolution
is better than nothing at all.

These do not need to bloat the binary, itself. They can be zlib-compressed
and stored in a lib dir, or something.

Also, a psychoanalyst mode could be added:

$ svn help me make the bugs go away, please?
// Maybe your life has something to do with this.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 20:50:00 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.