From 88f7b273bde97e2b4506b81b12e3b9180ff59fba Mon Sep 17 00:00:00 2001 From: "Valery V. Vorotyntsev" Date: Wed, 12 Dec 2007 10:15:16 +0100 Subject: Run.hs: fix documentation, cleanup whitespace darcs-hash:20071212091516-ae588-40ba4e8560f1132c6054b3b459c9fcbf9c7679e3.gz --- XMonad/Util/Run.hs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/XMonad/Util/Run.hs b/XMonad/Util/Run.hs index dead778..c9ac2a5 100644 --- a/XMonad/Util/Run.hs +++ b/XMonad/Util/Run.hs @@ -50,7 +50,7 @@ import Control.Monad -- For an example usage of 'runProcessWithInputAndWait' see -- "XMonad.Util.Dzen" --- | Returns Just output if the command succeeded, and Nothing if it didn't. +-- | Return output if the command succeeded, otherwise return @()@. -- This corresponds to dmenu's notion of exit code 1 for a cancelled invocation. runProcessWithInput :: FilePath -> [String] -> String -> IO String runProcessWithInput cmd args input = do @@ -104,10 +104,10 @@ seconds = fromEnum . (* 1000000) -- unsafeSpawn is an alias for XMonad's 'spawn', to remind one that use -- of it can be, well, unsafe. -- Examples: --- +-- -- > , ((modMask, xK_Print), unsafeSpawn "import -window root png:$HOME/xwd-$(date +%s)$$.png") -- > , ((modMask, xK_d ), safeSpawn "firefox" "") --- +-- -- Note that the unsafeSpawn example must be unsafe and not safe because -- it makes use of shell interpretation by relying on @$HOME@ and -- interpolation, whereas the safeSpawn example can be safe because -- cgit v1.2.3