From: Martin Quinson Date: Wed, 3 Feb 2021 19:31:35 +0000 (+0100) Subject: doc: borken link X-Git-Tag: v3.27~436^2~2 X-Git-Url: http://bilbo.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/ca976cdf0a8553c257a42a5b75947be2cad96f49 doc: borken link --- diff --git a/docs/source/outcomes.rst b/docs/source/outcomes.rst index b5af5ecd47..152fe61658 100644 --- a/docs/source/outcomes.rst +++ b/docs/source/outcomes.rst @@ -12,8 +12,8 @@ Using ``printf`` or ``println`` to display information is possible, but quickly should use SimGrid's logging facilities, that are inspired from `Log4J `_. This way, you can filter the messages at runtime, based on their severity and their topic. There is four main concepts in SimGrid's logging mechanism: -The **category** of a message represents its topic. These categories are organized as a hierarchy, loosely corresponding to SimGrid's modules architecture. `Existing categories -`_ are documented online, but some of them may be disabled depending on the compilation options. Use ``--help-log-categories`` on the command line to see +The **category** of a message represents its topic. These categories are organized as a hierarchy, loosely corresponding to SimGrid's modules architecture. :ref:`Existing categories +` are documented online, but some of them may be disabled depending on the compilation options. Use ``--help-log-categories`` on the command line to see the categories actually provided a given simulator. The message **priority** represents its severity. It can be one of ``trace``, ``debug``, ``verb``, ``info``, ``warn``, ``error`` and ``critical``. Every category has a configured