[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] Error handling updates
From: |
Thomas Zander |
Subject: |
Re: [Gnu-arch-users] Error handling updates |
Date: |
Wed, 24 Dec 2003 18:48:13 +0100 |
User-agent: |
KMail/1.5.94 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 24 December 2003 14:43, Aaron Bentley wrote:
> [meant to post to list, but just posted to Tom]
> Here's a patch that adds functions that can ensure a revision exists in
> the archive. It adapts tla get to issue the error "No such revision"
> when the user enters a valid, but non-existant revision name.
tla has been very correct in its error messages; which this one (from your
description) seems to fit right into.
It would be nice if the error message would end with a suggestion to get the
user on its way to solve the problem.
So in addition to 'No such revision' it would be nice to print on a second
line (to stderr)
"check valid revisions using 'tla revisions'"
Alternatively (less nice, but more in line with current tla)
" (try 'tla revisions')"
Just to be complete; I would really like to see more intelligent error
messages where possible; a few examples:
$ tla abrowse -A sftp://myserver/some/path
invalid archive name sftp://home/zander/sources/archives
Could additionaly give:
"Is the archive registered, see 'tla archives' and 'tla register-archive'"
$ tla register-archive address@hidden sftp://wrongFoo/wrongPath
$ tla abrowse -A address@hidden
ssh: : Name or service not known
Error reading from server
Could additionaly give:
"Check if registered archive is correct, see 'tla archives'"
Just my 0.02
- --
Thomas Zander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/6dFdCojCW6H2z/QRAj7HAKCijktE8jTeYEby4h/eixLbnpFXaQCgkSHG
lqy+Mb788IntE/oLoY7e9Hs=
=zVL5
-----END PGP SIGNATURE-----