gioGIODeveloperMatthiasClasenmclasen@redhat.comgio1User CommandsgioGIO commandline toolgiohelpCOMMANDgioversiongiocatLOCATIONgiocopyOPTIONSOURCEDESTINATIONgioinfoOPTIONLOCATIONgiolaunchDESKTOP-FILEFILE-ARGgiolistOPTIONLOCATIONgiomimeMIMETYPEHANDLERgiomkdirOPTIONLOCATIONgiomonitorOPTIONLOCATIONgiomountOPTIONLOCATIONgiomoveOPTIONSOURCEDESTINATIONgioopenLOCATIONgiorenameLOCATIONNAMEgioremoveOPTIONLOCATIONgiosaveOPTIONDESTINATIONgiosetOPTIONLOCATIONATTRIBUTEVALUEgiotrashOPTIONLOCATIONgiotreeOPTIONLOCATIONDescriptiongio is a utility that makes many of the GIO
features available from the commandline. In doing so, it provides
commands that are similar to traditional utilities, but let you
use GIO locations instead of local files: for example you can use
something like smb://server/resource/file.txt
as a location.Plain filenames which contain a colon will be interpreted as URIs
with an unknown protocol. To avoid this, prefix them with a path such as
./, or with the file: protocol.CommandshelpCOMMANDDisplays a short synopsis of the available commands or provides
detailed help on a specific command.versionPrints the GLib version to which gio
belongs.catLOCATIONConcatenates the given files and prints them to the standard
output.The cat command works just like the traditional cat utility.Note: just pipe through cat if you need its formatting options
like , or other.copyOPTIONSOURCEDESTINATIONCopies one or more files from SOURCE
to DESTINATION. If more than one source
is specified, the destination must be a directory.The copy command is similar to the traditional cp utility.Options, Don’t copy into DESTINATION even if it is a directory., Show progress., Prompt for confirmation before overwriting files.Preserve all attributes of copied files., Create backups of existing destination files., Never follow symbolic links.Use the default permissions of the current process for the destination file, rather than copying the permissions of the source file.infoOPTIONLOCATIONShows information about the given locations.The info command is similar to the traditional ls utility.Options, List writable attributes., Show information about the filesystem that the given
locations reside on.The attributes to get.Attributes can be specified with their GIO name, e.g.
standard::icon, or just by namespace, e.g. unix, or by *,
which matches all attributes. Several attributes or groups
of attributes can be specified, separated by comma.By default, all attributes are listed., Don’t follow symbolic links.launchDESKTOP-FILEFILE-ARGLaunch a desktop file from any location given.The launch command extends the behavior of the open command by allowing
any desktop file to be launched, not only those registered as file handlers.listOPTIONLOCATIONLists the contents of the given locations. If no location is
given, the contents of the current directory are shown.The list command is similar to the traditional ls utility.OptionsThe attributes to get.Attributes can be specified with their GIO name, e.g.
standard::icon, or just by namespace, e.g. unix, or by *,
which matches all attributes. Several attributes or groups
of attributes can be specified, separated by comma.By default, all attributes are listed., Show hidden files., Use a long listing format., Don’t follow symbolic links., Print display names., Print full URIs.mimeMIMETYPEHANDLERIf no handler is given, the mime command lists the
registered and recommended applications for the mimetype.
If a handler is given, it is set as the default handler for
the mimetype.Handlers must be specified by their desktop file name,
including the extension. Example: org.gnome.gedit.desktop.mkdirOPTIONLOCATIONCreates directories.The mkdir command is similar to the traditional mkdir utility.Options, Create parent directories when necessary.monitorOPTIONLOCATIONMonitors files or directories for changes, such as creation
deletion, content and attribute changes, and mount and unmount
operations affecting the monitored locations.The monitor command uses the GIO file monitoring APIs to do
its job. GIO has different implementations for different platforms.
The most common implementation on Linux uses inotify.Options, Monitor the given location as a directory. Normally,
the file type is used to determine whether to monitor a file or directory., Monitor the given location as a file. Normally,
the file type is used to determine whether to monitor a file or directory., Monitor the file directly. This allows changes made via hardlinks to be captured., Monitor the file directly, but don’t report changes., Report moves and renames as simple deleted/created events., Watch for mount events.mountOPTIONLOCATIONProvides commandline access to various aspects of GIO’s mounting
functionality.Mounting refers to the traditional concept of arranging multiple
file systems and devices in a single tree, rooted at /. Classical
mounting happens in the kernel and is controlled by the mount utility.
GIO expands this concept by introducing mount daemons that can make
file systems available to GIO applications without kernel
involvement.GIO mounts can require authentication, and the mount command
may ask for user IDs, passwords, and so on, when required.Options, Mount as mountable., Mount volume with device file, or other identifier., Unmount the location., Eject the location., Stop drive with device file., Unmount all mounts with the given scheme., Ignore outstanding file operations when unmounting or ejecting., Use an anonymous user when authenticating., List all GIO mounts., Monitor mount-related events., Show extra information.The numeric PIM when unlocking a VeraCrypt volume.Mount a TCRYPT hidden volume.Mount a TCRYPT system volume.moveOPTIONSOURCEDESTINATIONMoves one or more files from SOURCE
to DESTINATION. If more than one source
is specified, the destination must be a directory.The move command is similar to the traditional mv utility.Options, Don’t copy into DESTINATION even if it is a directory., Show progress., Prompt for confirmation before overwriting files., Create backups of existing destination files., Don’t use copy and delete fallback.openLOCATIONOpens files with the default application that is registered
to handle files of this type.GIO obtains this information from the shared-mime-info
database, with per-user overrides stored in
$XDG_DATA_HOME/applications/mimeapps.list.The mime command can be used to change the default handler for
a mimetype.Environment variables will not be set on the application, as it
may be an existing process which is activated to handle the new file.renameLOCATIONNAMERenames a file.The rename command is similar to the traditional rename utility.removeOPTIONLOCATIONDeletes each given file.This command removes files irreversibly. If you want a reversible
way to remove files, see the trash command.Note that not all URI schemes that are supported by GIO may
allow deletion of files.The remove command is similar to the traditional rm utility.Options, Ignore non-existent and non-deletable files.saveOPTIONDESTINATIONReads from standard input and saves the data to the given
location.This is similar to just redirecting output to a file using
traditional shell syntax, but the save command allows saving to
location that GIO can write to.Options, Back up existing destination files., Only create the destination if it doesn’t exist yet., Append to the end of the file., When creating, restrict access to the current user., When replacing, replace as if the destination did not exist., Print the new ETag in the end., The ETag of the file that is overwritten.setLOCATIONATTRIBUTEVALUESets a file attribute on a file.File attributes can be specified with their GIO name, e.g
standard::icon. Note that not all GIO file attributes are writable.
Use the option of the info command to list
writable file attributes.If the TYPE is unset,
VALUE does not have to be specified.
If the TYPE is stringv, multiple values can be given.Options, Specifies the type of the attribute. Supported
types are string, stringv,
bytestring, boolean,
uint32, int32,
uint64, int64 and unset.If the type is not specified, string is assumed., Unsets an attribute (same as setting it's type to unset)., Don’t follow symbolic links.trashOPTIONLOCATIONSends files or directories to the ‘Trashcan’ or restore them from
‘Trashcan’. This can be a different folder depending on where the file
is located, and not all file systems support this concept. In the common
case that the file lives inside a user’s home directory, the trash folder is
$XDG_DATA_HOME/Trash.Note that moving files to the trash does not free up space on
the file system until the ‘Trashcan’ is emptied. If you are interested
in deleting a file irreversibly, see the remove command.Inspecting and emptying the ‘Trashcan’ is normally supported by
graphical file managers such as Nautilus, but you can also see the
trash with the command: gio trash --list or
gio list trash://.Options, Ignore non-existent and non-deletable files.Empty the trash.List files in the trash with their original locationsRestore a file from trash to its original location. A URI beginning
with trash:// is expected here. If the original
directory doesn't exist, it will be recreated.treeOPTIONLOCATIONLists the contents of the given locations recursively, in a
tree-like format. If no location is given, it defaults to the current
directory.The tree command is similar to the traditional tree utility.Options, Show hidden files., Follow symbolic links.Exit statusOn success 0 is returned, a non-zero failure code otherwise.See Alsocat1,
cp1,
ls1,
mkdir1,
mv1,
rm1,
tree1.