= Description =

Here is a part from HelpOnParsers page:

==== ---Start example--- ====
A !ParserBase colorization parser understands the following arguments to a `#FORMAT` pi or a hashbang line. Just add those arguments after the name of the parser (`#FORMAT python start=10 step=10 numbering=on` or `#!python numbering=off`).

 numbering:: if line numbering should be added. defaults to 'on'. possible values: 'on', 'off' (no linenumbers, but javascript to add them), 'disable' (no line numbers at all)
==== ---End example--- ====

Actually there is no `numbering` option and you should use `numbers` otherwise.
== Steps to reproduce ==
## Describe the steps needed to reproduce the bug. If we can't reproduce it, we  probably can't fix it.

Compare this:
{{{#!python numbering=disable
def a
}}}
and this:
{{{#!python numbers=disable
def a
}}}


Here is a part of `parse_start_step` function in `ParserBase.py`, you see no `numbering` here, only 'numbers'
{{{#!python start=57
        if attrs.get('numbers','"on"')[1:-1].lower() in ('off', 'false', 'no'):
            nums = 0
        elif attrs.get('numbers','"on"')[1:-1].lower() in ('none', 'disable'):
            nums = -1
}}}
== Example ==
##Add URL that show the bug, screenshot or test wiki markup that fail...

URL: HelpOnParsers 

##attachment:screenshot.png

##{{{
##Example wiki markup that fail
##}}}

== Component selection ==

## Where you think is this bug happening ? (general, plugin [plugin name], theme [theme name], ...

 * general

== Details ==

## If you got a traceback, please save the traceback page as html and attach here:
## attachment:traceback.html

## if the bug is in this wiki, just kill the table and write: This Wiki.

## If a traceback is not available, please fill in the details here:
|| '''!MoinMoin Version''' || 1.5.8 ||

== Workaround ==
## How to deal with the bug until it is fixed

It's documentation bug.

Maybe it worth to add a page for people wondering why their numbering doesn't work.

= Discussion =


= Plan =
## This part is for Moin``Moin developers:

 * Priority: 
 * Assigned to: ThomasWaldmann
 * Status: fixed on MoinMaster:HelpOnParsers

----
## If you are a moin core developer, replace the category to Category* in these cases:
## Category MoinMoinNoBug - if this is not a bug.
## Category MoinMoinBugConfirmed - if you can confirm the bug on current code.
## Category MoinMoinBugFixed - after the bug is fixed in current code.
CategoryMoinMoinBugFixed