From 80ec1decc49c72efec2a8b87c06245c92c0ab807 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 11 Feb 2021 18:11:46 +0100 Subject: New upstream version 1.29.90 --- docs/libnm/html/NMClient.html | 47 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) (limited to 'docs/libnm/html/NMClient.html') diff --git a/docs/libnm/html/NMClient.html b/docs/libnm/html/NMClient.html index 1d2f15b3..7e7c131d 100644 --- a/docs/libnm/html/NMClient.html +++ b/docs/libnm/html/NMClient.html @@ -793,6 +793,14 @@ nm_client_dbus_set_property_finish () + + +void + + +nm_utils_print () + + @@ -4957,6 +4965,45 @@ nm_client_dbus_set_property_finish (

Since: 1.24

+
+
+

nm_utils_print ()

+
void
+nm_utils_print (int output_mode,
+                const char *msg);
+

The only purpose of this function is to give access to g_print() +or g_printerr() from pygobject. libnm can do debug logging by +setting LIBNM_CLIENT_DEBUG and uses thereby g_printerr() or +g_print(). A plain "print()" function in python is not in sync +with these functions (it implements additional buffering). By +using nm_utils_print(), the same logging mechanisms can be used.

+
+

Parameters

+
+++++ + + + + + + + + + + + + +

output_mode

if 1 it uses g_print(). If 2, it uses g_printerr(). +If 0, it uses either g_print() or g_printerr(), depending +on LIBNM_CLIENT_DEBUG (and the "stdout" flag).

 

msg

the message to print. The function does not append +a trailing newline.

 
+
+

Since: 1.30

+

Types and Values

-- cgit 1.3.0-6-gf8a5