Better validation errors
anatoly techtonik
<build xmlns:python="http://bitten.edgewall.org/tools/python"
xmlns:svn="http://bitten.edgewall.org/tools/svn">
<step id="update" description="Update source from repository">
<svn:update dir="/var/www/production"/>
</step>
<step id="test" description="Running Tests">
<sh:exec file="echo" args="Tests for WWW"/>
</step>
</build>
But it fails. The error is:
Warning: Failure parsing recipe: unbound prefix: line 7, column 4.
The reason is that sh namespace is not included. I knew what XML is
and namespaces are, but it took some time to pinpoint the problem
under affection of Friday evening syndrome. It would be useful to
transform "unbound prefix" error into something more obvious like
"unknown namespace 'sh'".
--
anatoly t.
Simon Cross
> But it fails. The error is:
> Warning: Failure parsing recipe: unbound prefix: line 7, column 4.
>
> The reason is that sh namespace is not included. I knew what XML is
> and namespaces are, but it took some time to pinpoint the problem
> under affection of Friday evening syndrome. It would be useful to
> transform "unbound prefix" error into something more obvious like
> "unknown namespace 'sh'".
I agree that your suggestion would be clearer but "line 7, column 4"
already nails down the error quite firmly. If this was a simple fix
I'd be keen but the error is thrown by the XML parser Bitten uses
(xml.dom.minidom) and I don't think it's worth catching the exception
and finishing around in the XML and exception message to make things
marginally better in this one case.
Schiavo
Simon
anatoly techtonik
>
> I agree that your suggestion would be clearer but "line 7, column 4"
> already nails down the error quite firmly. If this was a simple fix
> I'd be keen but the error is thrown by the XML parser Bitten uses
> (xml.dom.minidom) and I don't think it's worth catching the exception
> and finishing around in the XML and exception message to make things
> marginally better in this one case.
Significantly better! There is no line counters in recipe editor, so
you would have to count lines by hand. That's not a trivial task,
because what you see is not what you get - one line in minidom may be
equal to several wrapped lines in textarea. No notepad or wordpad for
windows have line counters, and I don't remember how to turn them on
in Vim either. So it is not superb at all from user perspective -
wasting time counting lines instead of concentrating on a real
problems.
The whole logic doesn't seem too complicated:
catch
match
replace
rethrow
(optionally): jQuery can catch line numbers and highlight them in
textarea.
Google Closure JS library can be of great help in designing such
component.
--
anatoly t.
potter
If you turn off Word-Wrap, then you can turn on the Status-Bar. With
the status bar on one can see what line and column your on.
Re: vim
I know it can be done, but I never do it. If I want to go to a
specific line I type the line number and then press 'G' (think go).
Example, to jump to line 32, type "32G". 'G' without a number prefix
takes you to the end of the file.
anatoly techtonik
> Re: notepad
>
> If you turn off Word-Wrap, then you can turn on the Status-Bar. With
> the status bar on one can see what line and column your on.
when Mercurial pops it up, using editor from Far Manager for all other
stuff, so there little chance for me to discover the fact.
> Re: vim
>
> I know it can be done, but I never do it. If I want to go to a
> specific line I type the line number and then press 'G' (think go).
> Example, to jump to line 32, type "32G". 'G' without a number prefix
> takes you to the end of the file.
is always present. Although I've never tried to discover editing in
wrapped line mode, so it may happen that there is just no such
ability, but there is a wrapped view that can be switched on/off with
F6.
Anti offtopic: http://bitten.edgewall.org/ticket/563
--
You received this message because you are subscribed to the Google Groups "Bitten" group.
To post to this group, send email to bit...@googlegroups.com.
To unsubscribe from this group, send email to bitten+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bitten?hl=en.
Olemis Lang
> On Feb 26, 10:13 pm, Simon Cross <hodges...@gmail.com> wrote:
>>
>> I agree that your suggestion would be clearer but "line 7, column 4"
>> already nails down the error quite firmly. If this was a simple fix
>> I'd be keen but the error is thrown by the XML parser Bitten uses
>> (xml.dom.minidom) and I don't think it's worth catching the exception
>> and finishing around in the XML and exception message to make things
>> marginally better in this one case.
>
> Significantly better! There is no line counters in recipe editor, so
> you would have to count lines by hand. That's not a trivial task,
> because what you see is not what you get - one line in minidom may be
> equal to several wrapped lines in textarea. No notepad or wordpad for
> windows have line counters,
;o)
> and I don't remember how to turn them on
> in Vim either.
<n> gg where n is the line number (e.g. in this case 7 gg )
> So it is not superb at all from user perspective -
> wasting time counting lines instead of concentrating on a real
> problems.
>
;o)
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
TracRpc: API v2: Fixing regression in dummy protocol providers -
http://bitbucket.org/osimons/trac-rpc-mq/changeset/807e2c73b6ec