luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-07-30 13:53:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

Don't use <envar> in docs

Browse Source 
Switch to simpler markdown, `foo`.
This commit is contained in:
Matthias Clasen
2014-02-05 19:32:41 -05:00
parent 2fda00af35
commit 111803030d
20 changed files with 151 additions and 153 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
glib/gfileutils.c
View File

@@ -72,8 +72,8 @@
*
* The pathname argument should be in the GLib file name encoding.
* On POSIX this is the actual on-disk encoding which might correspond
* to the locale settings of the process (or the
* <envar>G_FILENAME_ENCODING</envar> environment variable), or not.
* to the locale settings of the process (or the `G_FILENAME_ENCODING`
* environment variable), or not.
*
* On Windows the GLib file name encoding is UTF-8. Note that the
* Microsoft C library does not use UTF-8, but has separate APIs for
@@ -309,7 +309,7 @@ g_mkdir_with_parents (const gchar *pathname,
* %G_FILE_TEST_IS_SYMLINK will always return %FALSE. Testing for
* %G_FILE_TEST_IS_EXECUTABLE will just check that the file exists and
* its name indicates that it is executable, checking for well-known
* extensions and those listed in the <envar>PATHEXT</envar> environment variable.
* extensions and those listed in the `PATHEXT` environment variable.
*
* Return value: whether a test was %TRUE
**/