Hoogle Search
Within LTS Haskell 24.52 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
setDtlsConnectionRequireCloseNotify :: (MonadIO m, IsDtlsConnection o) => o -> Bool -> m ()gi-gio GI.Gio.Interfaces.DtlsConnection Set the value of the “require-close-notify” property. When overloading is enabled, this is equivalent to
set dtlsConnection [ #requireCloseNotify := value ]
fileEqual :: (HasCallStack, MonadIO m, IsFile a, IsFile b) => a -> b -> m Boolgi-gio GI.Gio.Interfaces.File Checks if the two given GFiles refer to the same file. Note that two GFiles that differ can still refer to the same file on the filesystem due to various forms of filename aliasing. This call does no blocking I/O.
-
gi-gio GI.Gio.Interfaces.File Returns the AppInfo that is registered as the default application to handle the file specified by file. If cancellable is not Nothing, then the operation can be cancelled by triggering the cancellable object from another thread. If the operation was cancelled, the error IOErrorEnumCancelled will be returned.
-
gi-gio GI.Gio.Interfaces.File Async version of fileQueryDefaultHandler. Since: 2.60
-
gi-gio GI.Gio.Interfaces.File Finishes a fileQueryDefaultHandlerAsync operation. Since: 2.60
fileQueryExists :: (HasCallStack, MonadIO m, IsFile a, IsCancellable b) => a -> Maybe b -> m Boolgi-gio GI.Gio.Interfaces.File Utility function to check if a particular file exists. This is implemented using fileQueryInfo and as such does blocking I/O. Note that in many cases it is racy to first check for file existence and then execute something based on the outcome of that, because the file might have been created or removed in between the operations. The general approach to handling that is to not check, but just do the operation and handle the errors as they come. As an example of race-free checking, take the case of reading a file, and if it doesn't exist, creating it. There are two racy versions: read it, and on error create it; and: check if it exists, if not create it. These can both result in two processes creating the file (with perhaps a partially written file as the result). The correct approach is to always try to create the file with fileCreate which will either atomically create the file or fail with a IOErrorEnumExists error. However, in many cases an existence check is useful in a user interface, for instance to make a menu item sensitive/insensitive, so that you don't have to fool users that something is possible and then just show an error dialog. If you do this, you should make sure to also handle the errors that can happen due to races when you execute the operation.
-
gi-gio GI.Gio.Interfaces.File Utility function to inspect the FileType of a file. This is implemented using fileQueryInfo and as such does blocking I/O. The primary use case of this method is to check if a file is a regular file, directory, or symlink. Since: 2.18
-
gi-gio GI.Gio.Interfaces.File Similar to fileQueryInfo, but obtains information about the filesystem the file is on, rather than the file itself. For instance the amount of space available and the type of the filesystem. The attributes value is a string that specifies the attributes that should be gathered. It is not an error if it's not possible to read a particular requested attribute from a file - it just won't be set. attributes should be a comma-separated list of attributes or attribute wildcards. The wildcard "*" means all attributes, and a wildcard like "filesystem::*" means all attributes in the filesystem namespace. The standard namespace for filesystem attributes is "filesystem". Common attributes of interest are FILE_ATTRIBUTE_FILESYSTEM_SIZE (the total size of the filesystem in bytes), FILE_ATTRIBUTE_FILESYSTEM_FREE (number of bytes available), and FILE_ATTRIBUTE_FILESYSTEM_TYPE (type of the filesystem). If cancellable is not Nothing, then the operation can be cancelled by triggering the cancellable object from another thread. If the operation was cancelled, the error IOErrorEnumCancelled will be returned. If the file does not exist, the IOErrorEnumNotFound error will be returned. Other errors are possible too, and depend on what kind of filesystem the file is on.
-
gi-gio GI.Gio.Interfaces.File Asynchronously gets the requested information about the filesystem that the specified file is on. The result is a FileInfo object that contains key-value attributes (such as type or size for the file). For more details, see fileQueryFilesystemInfo which is the synchronous version of this call. When the operation is finished, callback will be called. You can then call fileQueryInfoFinish to get the result of the operation.
-
gi-gio GI.Gio.Interfaces.File Finishes an asynchronous filesystem info query. See fileQueryFilesystemInfoAsync.