Fixed/Improved description of -rp/--relative-paths
run astyle
This commit is contained in:
parent
9f054fbb3c
commit
3eede5ba8c
|
@ -808,6 +808,10 @@ void CmdLineParser::PrintHelp() const
|
||||||
" Use relative paths in output. When given, <paths> are\n"
|
" Use relative paths in output. When given, <paths> are\n"
|
||||||
" used as base. You can separate multiple paths by ';'.\n"
|
" used as base. You can separate multiple paths by ';'.\n"
|
||||||
" Otherwise path where source files are searched is used.\n"
|
" Otherwise path where source files are searched is used.\n"
|
||||||
|
" We use string comparison to create relative paths, so\n"
|
||||||
|
" using e.g. ~ for home folder does not work. It is\n"
|
||||||
|
" currently only possible to apply the base paths to files\n"
|
||||||
|
" that are on a lower level in the directory tree.\n"
|
||||||
" --report-progress Report progress messages while checking a file.\n"
|
" --report-progress Report progress messages while checking a file.\n"
|
||||||
#ifdef HAVE_RULES
|
#ifdef HAVE_RULES
|
||||||
" --rule=<rule> Match regular expression.\n"
|
" --rule=<rule> Match regular expression.\n"
|
||||||
|
|
|
@ -366,12 +366,12 @@ Directory name is matched to all parts of the path.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>--rp</option></term>
|
<term><option>-rp</option></term>
|
||||||
<term><option>--rp=<paths></option></term>
|
<term><option>-rp=<paths></option></term>
|
||||||
<term><option>--relative-paths;</option></term>
|
<term><option>--relative-paths;</option></term>
|
||||||
<term><option>--relative-paths=<paths></option></term>
|
<term><option>--relative-paths=<paths></option></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Use relative paths in output. When given, <paths> are used as base. You can separate multiple paths by ';'. Otherwise path where source files are searched is used. E.g. if given value is test, when checking test/test.cpp, the path in output will be test.cpp instead of test/test.cpp. The feature uses string comparison to create relative paths, so using e.g. ~ for home folder does not work.</para>
|
<para>Use relative paths in output. When given, <paths> are used as base. You can separate multiple paths by ';'. Otherwise path where source files are searched is used. E.g. if given value is test, when checking test/test.cpp, the path in output will be test.cpp instead of test/test.cpp. The feature uses string comparison to create relative paths, so using e.g. ~ for home folder does not work. It is currently only possible to apply the base paths to files that are on a lower level in the directory tree.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
Loading…
Reference in New Issue