Flags

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

No description available in the introspection data.

Catch-all for unknown values

No guarantees about file consistency or durability. The most dangerous setting, which is slightly faster than other settings.

Guarantee file consistency: after a crash, either the old version of the file or the new version of the file will be available, but not a mixture. On Unix systems this equates to an fsync() on the file and use of an atomic rename() of the new version of the file over the old.

Guarantee file durability: after a crash, the new version of the file will be available. On Unix systems this equates to an fsync() on the file (if FileSetContentsFlagsConsistent is unset), or the effects of FileSetContentsFlagsConsistent plus an fsync() on the directory containing the file after calling rename().

Only apply consistency and durability guarantees if the file already exists. This may speed up file operations if the file doesn’t currently exist, but may result in a corrupted version of the new file if the system crashes while writing it.

Catch-all for unknown values

True if the file is a regular file (not a directory). Note that this test will also return True if the tested file is a symlink to a regular file.

True if the file is a symlink.

True if the file is a directory.

True if the file is executable.

True if the file exists. It may or may not be a regular file.

Catch-all for unknown values

behave the same as formatSize

include the exact number of bytes as part of the returned string. For example, "45.6 kB (45,612 bytes)".

use IEC (base 1024) units with "KiB"-style suffixes. IEC units should only be used for reporting things with a strong "power of 2" basis, like RAM sizes or RAID stripe sizes. Network and storage sizes should be reported in the normal SI units.

set the size as a quantity in bits, rather than bytes, and return units in bits. For example, ‘Mb’ rather than ‘MB’.

Catch-all for unknown values

set if the hook has not been destroyed

set if the hook is currently being run

A mask covering all bits reserved for hook flags; see HOOK_FLAG_USER_SHIFT

Catch-all for unknown values

There is data to read.

Data can be written (without blocking).

There is urgent data to read.

Error condition.

Hung up (the connection has been broken, usually for pipes and sockets).

Invalid request. The file descriptor is not open.

Catch-all for unknown values

turns on append mode, corresponds to O_APPEND (see the documentation of the UNIX open() syscall)

turns on nonblocking mode, corresponds to O_NONBLOCK/O_NDELAY (see the documentation of the UNIX open() syscall)

indicates that the io channel is readable. This flag cannot be changed.

indicates that the io channel is writable. This flag cannot be changed.

a misspelled version of gIOFLAGISWRITABLE that existed before the spelling was fixed in GLib 2.30. It is kept here for compatibility reasons. Deprecated since 2.30

indicates that the io channel is seekable, i.e. that iOChannelSeekPosition can be used on it. This flag cannot be changed.

the mask that specifies all the valid flags.

the mask of the flags that are returned from iOChannelGetFlags

the mask of the flags that the user can modify with iOChannelSetFlags

Catch-all for unknown values

No flags, default behaviour

Use this flag if you plan to write the (possibly modified) contents of the key file back to a file; otherwise all comments will be lost when the key file is written back.

Use this flag if you plan to write the (possibly modified) contents of the key file back to a file; otherwise only the translations for the current language will be written back.

Catch-all for unknown values

internal flag

internal flag

log level for errors, see g_error(). This level is also used for messages produced by g_assert().

log level for critical warning messages, see g_critical(). This level is also used for messages produced by g_return_if_fail() and g_return_val_if_fail().

log level for warnings, see g_warning()

log level for messages, see g_message()

log level for informational messages, see g_info()

log level for debug messages, see g_debug()

a mask including all log levels

Catch-all for unknown values

used to terminate the list of attributes to collect

collect the string pointer directly from the attribute_values[] array. Expects a parameter of type (const char **). If MarkupCollectTypeOptional is specified and the attribute isn't present then the pointer will be set to Nothing

as with MarkupCollectTypeString, but expects a parameter of type (char **) and strdups the returned pointer. The pointer must be freed with free

expects a parameter of type (gboolean *) and parses the attribute value as a boolean. Sets False if the attribute isn't present. Valid boolean values consist of (case-insensitive) "false", "f", "no", "n", "0" and "true", "t", "yes", "y", "1"

as with MarkupCollectTypeBoolean, but in the case of a missing attribute a value is set that compares equal to neither False nor True G_MARKUP_COLLECT_OPTIONAL is implied

can be bitwise ORed with the other fields. If present, allows the attribute not to appear. A default value is set depending on what value type is used

Catch-all for unknown values

flag you should not use

When this flag is set, CDATA marked sections are not passed literally to the passthrough function of the parser. Instead, the content of the section (without the <![CDATA[ and ]]>) is passed to the text function. This flag was added in GLib 2.12

Normally errors caught by GMarkup itself have line/column information prefixed to them to let the caller know the location of the error. When this flag is set the location information is also prefixed to errors generated by the MarkupParser implementation functions

Ignore (don't report) qualified attributes and tags, along with their contents. A qualified attribute or tag is one that contains ':' in its name (ie: is in another namespace). Since: 2.40.

Catch-all for unknown values

No flags. Since: 2.42.

The option doesn't appear in --help output.

The option appears in the main section of the --help output, even if it is defined in a group.

For options of the OptionArgNone kind, this flag indicates that the sense of the option is reversed.

For options of the OptionArgCallback kind, this flag indicates that the callback does not take any argument (like a OptionArgNone option). Since 2.8

For options of the OptionArgCallback kind, this flag indicates that the argument should be passed to the callback in the GLib filename encoding rather than UTF-8. Since 2.8

For options of the OptionArgCallback kind, this flag indicates that the argument supply is optional. If no argument is given then data of GOptionParseFunc will be set to NULL. Since 2.8

This flag turns off the automatic conflict resolution which prefixes long option names with groupname- if there is a conflict. This option should only be used in situations where aliasing is necessary to model some legacy commandline interface. It is not safe to use this option, unless all option groups are under your direct control. Since 2.8.

Catch-all for unknown values

Letters in the pattern match both upper- and lowercase letters. This option can be changed within a pattern by a "(?i)" option setting.

By default, GRegex treats the strings as consisting of a single line of characters (even if it actually contains newlines). The "start of line" metacharacter ("^") matches only at the start of the string, while the "end of line" metacharacter ("$") matches only at the end of the string, or before a terminating newline (unless G_REGEX_DOLLAR_ENDONLY is set). When G_REGEX_MULTILINE is set, the "start of line" and "end of line" constructs match immediately following or immediately before any newline in the string, respectively, as well as at the very start and end. This can be changed within a pattern by a "(?m)" option setting.

A dot metacharacter (".") in the pattern matches all characters, including newlines. Without it, newlines are excluded. This option can be changed within a pattern by a ("?s") option setting.

Whitespace data characters in the pattern are totally ignored except when escaped or inside a character class. Whitespace does not include the VT character (code 11). In addition, characters between an unescaped "#" outside a character class and the next newline character, inclusive, are also ignored. This can be changed within a pattern by a "(?x)" option setting.

The pattern is forced to be "anchored", that is, it is constrained to match only at the first matching point in the string that is being searched. This effect can also be achieved by appropriate constructs in the pattern itself such as the "^" metacharacter.

A dollar metacharacter ("$") in the pattern matches only at the end of the string. Without this option, a dollar also matches immediately before the final character if it is a newline (but not before any other newlines). This option is ignored if G_REGEX_MULTILINE is set.

Inverts the "greediness" of the quantifiers so that they are not greedy by default, but become greedy if followed by "?". It can also be set by a "(?U)" option setting within the pattern.

Usually strings must be valid UTF-8 strings, using this flag they are considered as a raw sequence of bytes.

Disables the use of numbered capturing parentheses in the pattern. Any opening parenthesis that is not followed by "?" behaves as if it were followed by "?:" but named parentheses can still be used for capturing (and they acquire numbers in the usual way).

Optimize the regular expression. If the pattern will be used many times, then it may be worth the effort to optimize it to improve the speed of matches.

Limits an unanchored pattern to match before (or at) the first newline. Since: 2.34

Names used to identify capturing subpatterns need not be unique. This can be helpful for certain types of pattern when it is known that only one instance of the named subpattern can ever be matched.

Usually any newline character or character sequence is recognized. If this option is set, the only recognized newline character is '\r'.

Usually any newline character or character sequence is recognized. If this option is set, the only recognized newline character is '\n'.

Usually any newline character or character sequence is recognized. If this option is set, the only recognized newline character sequence is '\r\n'.

Usually any newline character or character sequence is recognized. If this option is set, the only recognized newline character sequences are '\r', '\n', and '\r\n'. Since: 2.34

Usually any newline character or character sequence is recognised. If this option is set, then "\R" only recognizes the newline characters '\r', '\n' and '\r\n'. Since: 2.34

Changes behaviour so that it is compatible with JavaScript rather than PCRE. Since: 2.34

Catch-all for unknown values

The pattern is forced to be "anchored", that is, it is constrained to match only at the first matching point in the string that is being searched. This effect can also be achieved by appropriate constructs in the pattern itself such as the "^" metacharacter.

Specifies that first character of the string is not the beginning of a line, so the circumflex metacharacter should not match before it. Setting this without G_REGEX_MULTILINE (at compile time) causes circumflex never to match. This option affects only the behaviour of the circumflex metacharacter, it does not affect "\A".

Specifies that the end of the subject string is not the end of a line, so the dollar metacharacter should not match it nor (except in multiline mode) a newline immediately before it. Setting this without G_REGEX_MULTILINE (at compile time) causes dollar never to match. This option affects only the behaviour of the dollar metacharacter, it does not affect "\Z" or "\z".

An empty string is not considered to be a valid match if this option is set. If there are alternatives in the pattern, they are tried. If all the alternatives match the empty string, the entire match fails. For example, if the pattern "a?b?" is applied to a string not beginning with "a" or "b", it matches the empty string at the start of the string. With this flag set, this match is not valid, so GRegex searches further into the string for occurrences of "a" or "b".

Turns on the partial matching feature, for more documentation on partial matching see matchInfoIsPartialMatch.

Overrides the newline definition set when creating a new Regex, setting the '\r' character as line terminator.

Overrides the newline definition set when creating a new Regex, setting the '\n' character as line terminator.

Overrides the newline definition set when creating a new Regex, setting the '\r\n' characters sequence as line terminator.

Overrides the newline definition set when creating a new Regex, any Unicode newline sequence is recognised as a newline. These are '\r', '\n' and '\rn', and the single characters U+000B LINE TABULATION, U+000C FORM FEED (FF), U+0085 NEXT LINE (NEL), U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR.

Overrides the newline definition set when creating a new Regex; any '\r', '\n', or '\r\n' character sequence is recognized as a newline. Since: 2.34

Overrides the newline definition for "\R" set when creating a new Regex; only '\r', '\n', or '\r\n' character sequences are recognized as a newline by "\R". Since: 2.34

Overrides the newline definition for "\R" set when creating a new Regex; any Unicode newline character or character sequence are recognized as a newline by "\R". These are '\r', '\n' and '\rn', and the single characters U+000B LINE TABULATION, U+000C FORM FEED (FF), U+0085 NEXT LINE (NEL), U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR. Since: 2.34

An alias for G_REGEX_MATCH_PARTIAL. Since: 2.34

Turns on the partial matching feature. In contrast to to G_REGEX_MATCH_PARTIAL_SOFT, this stops matching as soon as a partial match is found, without continuing to search for a possible complete match. See matchInfoIsPartialMatch for more information. Since: 2.34

Like G_REGEX_MATCH_NOTEMPTY, but only applied to the start of the matched string. For anchored patterns this can only happen for pattern containing "\K". Since: 2.34

Catch-all for unknown values

no flags, default behaviour

the parent's open file descriptors will be inherited by the child; otherwise all descriptors except stdin, stdout and stderr will be closed before calling exec() in the child.

the child will not be automatically reaped; you must use g_child_watch_add() yourself (or call waitpid() or handle SIGCHLD yourself), or the child will become a zombie.

argv[0] need not be an absolute path, it will be looked for in the user's PATH.

the child's standard output will be discarded, instead of going to the same location as the parent's standard output.

the child's standard error will be discarded.

the child will inherit the parent's standard input (by default, the child's standard input is attached to /dev/null).

the first element of argv is the file to execute, while the remaining elements are the actual argument vector to pass to the file. Normally spawnAsyncWithPipes uses argv[0] as the file to execute, and passes all of argv to the child.

if argv[0] is not an absolute path, it will be looked for in the PATH from the passed child environment. Since: 2.34

create all pipes with the O_CLOEXEC flag set. Since: 2.40

Catch-all for unknown values

If this flag is given, the child process will inherit the parent's stdin. Otherwise, the child's stdin is redirected to /dev/null.

If this flag is given, the child process will inherit the parent's stdout. Otherwise, the child's stdout will not be visible, but it will be captured to allow later tests with g_test_trap_assert_stdout().

If this flag is given, the child process will inherit the parent's stderr. Otherwise, the child's stderr will not be visible, but it will be captured to allow later tests with g_test_trap_assert_stderr().

Catch-all for unknown values

Redirect stdout of the test child to /dev/null so it cannot be observed on the console during test runs. The actual output is still captured though to allow later tests with g_test_trap_assert_stdout().

Redirect stderr of the test child to /dev/null so it cannot be observed on the console during test runs. The actual output is still captured though to allow later tests with g_test_trap_assert_stderr().

If this flag is given, stdin of the child process is shared with stdin of its parent process. It is redirected to /dev/null otherwise.

Catch-all for unknown values

only leaf nodes should be visited. This name has been introduced in 2.6, for older version use TraverseFlagsLeafs.

only non-leaf nodes should be visited. This name has been introduced in 2.6, for older version use TraverseFlagsNonLeafs.

all nodes should be visited.

a mask of all traverse flags.

identical to TraverseFlagsLeaves.

identical to TraverseFlagsNonLeaves.

Catch-all for unknown values

No flags set.

Parse the URI more relaxedly than the RFC 3986 grammar specifies, fixing up or ignoring common mistakes in URIs coming from external sources. This is also needed for some obscure URI schemes where ; separates the host from the path. Don’t use this flag unless you need to.

The userinfo field may contain a password, which will be separated from the username by :.

The userinfo may contain additional authentication-related parameters, which will be separated from the username and/or password by ;.

When parsing a URI, this indicates that %-encoded characters in the userinfo, path, query, and fragment fields should not be decoded. (And likewise the host field if UriFlagsNonDns is also set.) When building a URI, it indicates that you have already %-encoded the components, and so Uri should not do any encoding itself.

The host component should not be assumed to be a DNS hostname or IP address (for example, for smb URIs with NetBIOS hostnames).

Same as UriFlagsEncoded, for the query field only.

Same as UriFlagsEncoded, for the path only.

Same as UriFlagsEncoded, for the fragment only.

A scheme-based normalization will be applied. For example, when parsing an HTTP URI changing omitted path to / and omitted port to 80; and when building a URI, changing empty path to / and default port 80). This only supports a subset of known schemes. (Since: 2.68)

Catch-all for unknown values

No flags set.

Hide the userinfo.

Hide the password.

Hide the auth_params.

Hide the query.

Hide the fragment.

Catch-all for unknown values

No flags set.

Parameter names are case insensitive.

Replace + with space character. Only useful for URLs on the web, using the https or http schemas.

See UriFlagsParseRelaxed.

Catch-all for unknown values