Show bugs reported on Scilab bugzilla or forge bugs trackers, or as ATOMS comments
uman bugNumber wb uman item wb uman item1|item2.. wb uman author>item.. wb uman author1|author2|..>item.. wb uman author><Ndays wb uman section/>item.. wb uman section/><Ndays wb uman section1|section2|../author1|author2|..>item1|item2|..<Ndays wb uman "section1|section2|.. / author1|author2|.. > item1 | item2 |..<Ndays" wb
wb
are uman's options making uman
working in "bug query" mode.
The uman
x
option setting the priority
to features eXternal to Scilab (for instance ATOMS modules
features) can be taken into account if only one item is
provided. Otherwise, it will be ignored.
After installing or uninstalling an external module,
the r
option will refresh
uman
references to make it informed
about changes and take them into account.
Examples using r
and
x
in wb
mode are
provided herebelow.
Integer > 76 (entered as text): id of the targeted bug report on the Scilab Bugzilla bugs tracker.
Case-insensitive words or text expressions that must be searched for in the title of bugs reports. Reports with a title having at least one of the listed items are selected.
Neither exclusion ~ (NOT)
nor
& (AND)
conjunction operators are
available for items.
Case-insensitive names of bugs reporters or commenters on Scilab bugzilla bug tracker.
Positive integer (entered as text): maximum age of reports changes of bugs to be selected, expressed in number of days from now.
Case-insensitive name(s) of components/categories in which the selected bugs are registered, provided that the Scilab's bug tracker is actually targeted.
SUPPORTED BUGS CATEGORIES:
|
|
AND: "Bug tracker", Codereview, "File Exchange", Forge, "Mailing Lists", "Online Help", WebSite, Wiki
/ | Separator between sections
and authors lists.
When no sections are specified, "/" is
not needed. |
> | authors >
items separator.
When no authors are specified, ">" is not needed. |
< | items <
maximum age of bugs changes
separator. When no age is specified,
"<" is not required. |
| | OR conjunction between selected authors or selected items. |
"..." | When there is at least one space in any part of the search pattern (authors, items, bugs age), the whole pattern must be specified between single or double quotes. |
uman .. wb
runs the web browser defined in
your Scilab preferences and opens an URL searching in online Scilab bugs
trackers for the provided item(s) and criteria.
![]() | uman .. wb requires an active internet
connexion. |
uman .. wb
is console-quiet.
When the pattern is a bugNumber
: the page of
the bug numbered and documented on Scilab's bugzilla is displayed.
Example: uman 11625 wb
Otherwise: How does uman .. wb
process the query?
If no item, or several |
-separated items
are provided, uman
will query the Scilab
bugzilla bug tracker.
Otherwise: uman
looks for the item
among native Scilab functions and other Scilab ressources
installed on your computer, as it does in normal console mode.
Then, according to the type of Scilab ressource where the item
has been found, the bug query is routed as it follows:
If the ressource is Scilab itself, Bugzilla is targeted.
If the ressource is an ATOMS module having a Scilab
public forge, or if it is a package out of ATOMS but
having a Scilab public forge registered by uman:
the bug tracker of the forge is targeted. The list of
documented bugs related to the item
is selected and displayed on the tickets page of the Forge
http://forge.scilab.org/index.php/p/<module_name>/issues/.
If the ressource is an ATOMS module without Scilab public forge: The comments section of its ATOMS page is targeted, where bugs may be reported.
If the ressource is a known FileExchange item: The comments section of the FileExchange page is targeted, where bugs may be reported.
If the ressource is out of ATOMS, FileExchange, and Scilab forges, but is uman-registered and has a known website: Its website is targeted.
If the item has been found in none of known ressources registered in uman: Scilab's bugzilla is targeted.
![]() | In wb mode, uman does not perform
any redirection if it does not find the item in primary
registered ressources.
Example: |
Section(s)
, author(s)
,
item(s)
, and bug-changes maximum age
Ndays
are taken into account only when Bugzilla is targeted.
Otherwise, they are ignored.
None of possible items, sections, authors, or age of bugs-change specifications is mandatory, but giving at least one of them is more efficient ;)
When several types of criteria are provided (section, author, item, bug age), only bugs reports fulfilling all of them are selected.
![]() | Queries sent to Bugzilla and that are not about a given bug number
are processed as a regular expression. However, presently, special
characters such as wildcards ., * or other ones
are protected and have no special meaning and role. |
// ====== ALIVE INTERNET CONNEXION REQUIRED ====== // // Documented bugs online: The "wb" options // ---------------------------------------- uman 11625 wb // Displays the bugzilla page of the bug #11625 uman ode wb // For any Scilab internal function, on bugzilla, well sorted uman cshift wb // For functions registered on FileExchange, bugs may be // reported as users comments on the dedicated online page uman gpib wb // Only registered as external ressource => website targeted. uman flipud wb // Unknown pattern. The existing redirection to flipdim() // is ignored => "flipud" is searched for as is on Bugzilla. uman cholesky wb // For any unknown pattern: searched as is on bugzilla uman ndgrid|meshgrid wb // Bug reports about ndgrid OR meshgrid, on Bugzilla, // as always when several items are indicated. uman graphics/><30 wb // Reports in the graphics category, changed max 30 days ago uman maths/gougeon> wb // Reports / comments by gougeon in the Maths category uman helpsys/gougeon>console wb // Reports / comments by gougeon about "console" // in the "help system" category uman "<10" wb // Reports changed within the last 10 days. // Examples with an external toolbox installed // ------------------------------------------- yn = atomsIsInstalled("plotlib"); atomsInstall plotlib ; // Let's instal Plotlib atomsIsLoaded plotlib // => %F: no need to be loaded uman plot rwb // After a module installation or uninstallation, we must // "r"efresh uman once with "r" option, to make it aware of it. // "plot" exists in Scilab as well as in "plotlib" // By default, the Scilab native entry is considered. So here // "plot" is search on Scilab Bugzilla, as a part of Scilab. uman plot xwb // When we use the "x" option, priority is given to the eXternal // feature => the ticket page of plotlib is addressed on the // plotlib forge, instead of Scilab Bugzilla. uman quiver wb // quiver is in plotlib, not in Scilab => no need to use the // "x" option: the tickets page of plotlib is directly targeted // on its forge. if ~yn, atomsRemove("plotlib"), end // cleaning after the example
Version | Description |
2.0, 2016-04-06 | Separate help page for "uman .. wb" |
1.0, 2015-03-22 | First uman release |