summaryrefslogtreecommitdiffstats
path: root/include/osmocom/vty/ports.h
diff options
context:
space:
mode:
authorNeels Hofmeyr <neels@hofmeyr.de>2017-10-22 02:31:33 +0200
committerHarald Welte <laforge@gnumonks.org>2017-12-10 13:34:35 +0000
commit453e37e3c8322cd200a6f803579c55753e866c7f (patch)
treef03e0340953b4c1d04dace39ef2b53c0dc67b97b /include/osmocom/vty/ports.h
parentf7162771d78efb2d9d81caae0b10801771a39645 (diff)
VTY reference: use node names as section names
In 'show online-help' output, add the node names (currently all derived from the prompt) as <node><name> entry, so that in the osmo-gsm-manuals, each section of node commands gets a title. So far, each section of commands has no name at all, and it is entirely up for guessing which part of the VTY the commands are about. Node section names, e.g. for OsmoHLR, will be like 1 VTY reference 1.4 config 1.5 config-log 1.6 config-line 1.7 config-ctrl 1.8 config-hlr 1.9 config-hlr-gsup Before this patch, all but '1 VTY reference' were plain empty. A better solution would be to list the actual command name that enters the node, and to nest the commands identically to VTY node nesting, but since this information is currently hidden in node command implementations, it is impossible to derive it. So we should actually make the VTY reflect the node nesting structure in its data model, which would resolve both the accurate node name problem as well as produce well-structured output to generate the VTY references from. This patch is a workaround for lack of a more profound fix of the VTY data model. At least it makes the VTY references' sections even remotely useful. Change-Id: Iaf745b2ab3d9b02fc47025a0eba3beb711068bfe
Diffstat (limited to 'include/osmocom/vty/ports.h')
0 files changed, 0 insertions, 0 deletions