From bodnarlajoska at gmail.com Wed Feb 1 17:36:03 2017 From: bodnarlajoska at gmail.com (Lajos Bodnar) Date: Wed, 1 Feb 2017 18:36:03 +0100 Subject: [xmonad] dual monitor Message-ID: Hi all. I'm new in the mail list, and sorry for my english ... I tried to set up my wm for dual monitor with these keyboard settings: -- mod-[1..9], Switch to workspace N -- mod-shift-[1..9], Move client to workspace N -- [((m .|. mod4Mask, k), windows $ f i) | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] ++ -- -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 -- [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust (windows . f)) | (key, sc) <- zip [xK_w, xK_e] [0..] , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]] I exprerienced that when I switch workspace the opened windows moved the new workspace from the inactive screen. If the inactive screen is empty in the workspace where I have just moved then a window will fill it. I hope it is understandable for you. Any idea ? What is wrong ? What causes it ? Regards, Lajos -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Wed Feb 1 21:16:34 2017 From: allbery.b at gmail.com (Brandon Allbery) Date: Wed, 1 Feb 2017 16:16:34 -0500 Subject: [xmonad] dual monitor In-Reply-To: References: Message-ID: You don't need to add keybindings, they are default. I assume this means you have been using the bad "example config" that overrides every possible setting with the defaults from some particular version instead of inheriting the defaults, and will need to be extremely careful about xmonad upgrades because your config won't magically rewrite itself to be compatible. (I think mod-shift-space is the one that will bite you in 0.13.) I *think* you are talking about https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar wrote: > Hi all. > I'm new in the mail list, and sorry for my english ... > > I tried to set up my wm for dual monitor with these keyboard settings: > -- mod-[1..9], Switch to workspace N > -- mod-shift-[1..9], Move client to workspace N > -- > [((m .|. mod4Mask, k), windows $ f i) > | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] > , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] > ++ > -- > -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 > -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 > -- > [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust (windows > . f)) > | (key, sc) <- zip [xK_w, xK_e] [0..] > , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]] > > I exprerienced that when I switch workspace the opened windows moved the > new workspace from the inactive screen. If the inactive screen is empty in > the workspace where I have just moved then a window will fill it. I hope it > is understandable for you. > Any idea ? > What is wrong ? What causes it ? > > Regards, > Lajos > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > > -- brandon s allbery kf8nh sine nomine associates allbery.b at gmail.com ballbery at sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From bodnarlajoska at gmail.com Wed Feb 1 21:27:20 2017 From: bodnarlajoska at gmail.com (Lajos Bodnar) Date: Wed, 1 Feb 2017 22:27:20 +0100 Subject: [xmonad] dual monitor In-Reply-To: References: Message-ID: Thanks for the answers, I will check what Brandon mentioned. On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery wrote: > You don't need to add keybindings, they are default. I assume this means > you have been using the bad "example config" that overrides every possible > setting with the defaults from some particular version instead of > inheriting the defaults, and will need to be extremely careful about xmonad > upgrades because your config won't magically rewrite itself to be > compatible. (I think mod-shift-space is the one that will bite you in 0.13.) > > I *think* you are talking about https://wiki.haskell. > org/Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view > > On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar > wrote: > >> Hi all. >> I'm new in the mail list, and sorry for my english ... >> >> I tried to set up my wm for dual monitor with these keyboard settings: >> -- mod-[1..9], Switch to workspace N >> -- mod-shift-[1..9], Move client to workspace N >> -- >> [((m .|. mod4Mask, k), windows $ f i) >> | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] >> , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] >> ++ >> -- >> -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 >> -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 >> -- >> [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust >> (windows . f)) >> | (key, sc) <- zip [xK_w, xK_e] [0..] >> , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]] >> >> I exprerienced that when I switch workspace the opened windows moved the >> new workspace from the inactive screen. If the inactive screen is empty in >> the workspace where I have just moved then a window will fill it. I hope it >> is understandable for you. >> Any idea ? >> What is wrong ? What causes it ? >> >> Regards, >> Lajos >> >> _______________________________________________ >> xmonad mailing list >> xmonad at haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >> >> > > > -- > brandon s allbery kf8nh sine nomine > associates > allbery.b at gmail.com > ballbery at sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bodnarlajoska at gmail.com Thu Feb 2 05:57:44 2017 From: bodnarlajoska at gmail.com (Lajos Bodnar) Date: Thu, 2 Feb 2017 06:57:44 +0100 Subject: [xmonad] dual monitor In-Reply-To: References: Message-ID: Hi! Morning :) I tried what Brandon mentioned before, but the result is same. Did you send me a correct link about a correct xmonad.hs ? Maybe can I make a configuration where the half of the workspaces resides the screen 1 and the other ones resides screen 2 ? Regards, Lajos On Wed, Feb 1, 2017 at 10:27 PM, Lajos Bodnar wrote: > Thanks for the answers, I will check what Brandon mentioned. > > On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery > wrote: > >> You don't need to add keybindings, they are default. I assume this means >> you have been using the bad "example config" that overrides every possible >> setting with the defaults from some particular version instead of >> inheriting the defaults, and will need to be extremely careful about xmonad >> upgrades because your config won't magically rewrite itself to be >> compatible. (I think mod-shift-space is the one that will bite you in 0.13.) >> >> I *think* you are talking about https://wiki.haskell.org >> /Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view >> >> On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar >> wrote: >> >>> Hi all. >>> I'm new in the mail list, and sorry for my english ... >>> >>> I tried to set up my wm for dual monitor with these keyboard settings: >>> -- mod-[1..9], Switch to workspace N >>> -- mod-shift-[1..9], Move client to workspace N >>> -- >>> [((m .|. mod4Mask, k), windows $ f i) >>> | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] >>> , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] >>> ++ >>> -- >>> -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 >>> -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 >>> -- >>> [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust >>> (windows . f)) >>> | (key, sc) <- zip [xK_w, xK_e] [0..] >>> , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]] >>> >>> I exprerienced that when I switch workspace the opened windows moved the >>> new workspace from the inactive screen. If the inactive screen is empty in >>> the workspace where I have just moved then a window will fill it. I hope it >>> is understandable for you. >>> Any idea ? >>> What is wrong ? What causes it ? >>> >>> Regards, >>> Lajos >>> >>> _______________________________________________ >>> xmonad mailing list >>> xmonad at haskell.org >>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>> >>> >> >> >> -- >> brandon s allbery kf8nh sine nomine >> associates >> allbery.b at gmail.com >> ballbery at sinenomine.net >> unix, openafs, kerberos, infrastructure, xmonad >> http://sinenomine.net >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmwit at dmwit.com Thu Feb 2 06:24:36 2017 From: dmwit at dmwit.com (Daniel Wagner) Date: Wed, 1 Feb 2017 22:24:36 -0800 Subject: [xmonad] dual monitor In-Reply-To: References: Message-ID: Can you show the config you tried after following the greedyView FAQ? That really should fix the behavior you're describing. The second feature you describe can *also* be done, see: http://hackage.haskell.org/package/xmonad-contrib-0.12/docs/XMonad-Layout-IndependentScreens.html ~d On Wed, Feb 1, 2017 at 9:57 PM, Lajos Bodnar wrote: > Hi! > Morning :) > I tried what Brandon mentioned before, but the result is same. > Did you send me a correct link about a correct xmonad.hs ? > Maybe can I make a configuration where the half of the workspaces resides > the screen 1 and the other ones resides screen 2 ? > > Regards, > Lajos > > > On Wed, Feb 1, 2017 at 10:27 PM, Lajos Bodnar > wrote: > >> Thanks for the answers, I will check what Brandon mentioned. >> >> On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery >> wrote: >> >>> You don't need to add keybindings, they are default. I assume this means >>> you have been using the bad "example config" that overrides every possible >>> setting with the defaults from some particular version instead of >>> inheriting the defaults, and will need to be extremely careful about xmonad >>> upgrades because your config won't magically rewrite itself to be >>> compatible. (I think mod-shift-space is the one that will bite you in 0.13.) >>> >>> I *think* you are talking about https://wiki.haskell.org >>> /Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view >>> >>> On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar >>> wrote: >>> >>>> Hi all. >>>> I'm new in the mail list, and sorry for my english ... >>>> >>>> I tried to set up my wm for dual monitor with these keyboard settings: >>>> -- mod-[1..9], Switch to workspace N >>>> -- mod-shift-[1..9], Move client to workspace N >>>> -- >>>> [((m .|. mod4Mask, k), windows $ f i) >>>> | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] >>>> , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] >>>> ++ >>>> -- >>>> -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 >>>> -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 >>>> -- >>>> [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust >>>> (windows . f)) >>>> | (key, sc) <- zip [xK_w, xK_e] [0..] >>>> , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]] >>>> >>>> I exprerienced that when I switch workspace the opened windows moved >>>> the new workspace from the inactive screen. If the inactive screen is empty >>>> in the workspace where I have just moved then a window will fill it. I hope >>>> it is understandable for you. >>>> Any idea ? >>>> What is wrong ? What causes it ? >>>> >>>> Regards, >>>> Lajos >>>> >>>> _______________________________________________ >>>> xmonad mailing list >>>> xmonad at haskell.org >>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>>> >>>> >>> >>> >>> -- >>> brandon s allbery kf8nh sine nomine >>> associates >>> allbery.b at gmail.com >>> ballbery at sinenomine.net >>> unix, openafs, kerberos, infrastructure, xmonad >>> http://sinenomine.net >>> >> >> > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bodnarlajoska at gmail.com Thu Feb 2 07:17:42 2017 From: bodnarlajoska at gmail.com (Lajos Bodnar) Date: Thu, 2 Feb 2017 08:17:42 +0100 Subject: [xmonad] dual monitor In-Reply-To: References: Message-ID: Hi Daniel. I'm in my workplace and I will look at it home. thanks Lajos On Thu, Feb 2, 2017 at 7:24 AM, Daniel Wagner wrote: > Can you show the config you tried after following the greedyView FAQ? That > really should fix the behavior you're describing. > > The second feature you describe can *also* be done, see: > http://hackage.haskell.org/package/xmonad-contrib-0.12/docs/XMonad-Layout- > IndependentScreens.html > > ~d > > On Wed, Feb 1, 2017 at 9:57 PM, Lajos Bodnar > wrote: > >> Hi! >> Morning :) >> I tried what Brandon mentioned before, but the result is same. >> Did you send me a correct link about a correct xmonad.hs ? >> Maybe can I make a configuration where the half of the workspaces resides >> the screen 1 and the other ones resides screen 2 ? >> >> Regards, >> Lajos >> >> >> On Wed, Feb 1, 2017 at 10:27 PM, Lajos Bodnar >> wrote: >> >>> Thanks for the answers, I will check what Brandon mentioned. >>> >>> On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery >>> wrote: >>> >>>> You don't need to add keybindings, they are default. I assume this >>>> means you have been using the bad "example config" that overrides every >>>> possible setting with the defaults from some particular version instead of >>>> inheriting the defaults, and will need to be extremely careful about xmonad >>>> upgrades because your config won't magically rewrite itself to be >>>> compatible. (I think mod-shift-space is the one that will bite you in 0.13.) >>>> >>>> I *think* you are talking about https://wiki.haskell.org >>>> /Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view >>>> >>>> On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar >>>> wrote: >>>> >>>>> Hi all. >>>>> I'm new in the mail list, and sorry for my english ... >>>>> >>>>> I tried to set up my wm for dual monitor with these keyboard settings: >>>>> -- mod-[1..9], Switch to workspace N >>>>> -- mod-shift-[1..9], Move client to workspace N >>>>> -- >>>>> [((m .|. mod4Mask, k), windows $ f i) >>>>> | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] >>>>> , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] >>>>> ++ >>>>> -- >>>>> -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 >>>>> -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 >>>>> -- >>>>> [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust >>>>> (windows . f)) >>>>> | (key, sc) <- zip [xK_w, xK_e] [0..] >>>>> , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]] >>>>> >>>>> I exprerienced that when I switch workspace the opened windows moved >>>>> the new workspace from the inactive screen. If the inactive screen is empty >>>>> in the workspace where I have just moved then a window will fill it. I hope >>>>> it is understandable for you. >>>>> Any idea ? >>>>> What is wrong ? What causes it ? >>>>> >>>>> Regards, >>>>> Lajos >>>>> >>>>> _______________________________________________ >>>>> xmonad mailing list >>>>> xmonad at haskell.org >>>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>>>> >>>>> >>>> >>>> >>>> -- >>>> brandon s allbery kf8nh sine nomine >>>> associates >>>> allbery.b at gmail.com >>>> ballbery at sinenomine.net >>>> unix, openafs, kerberos, infrastructure, xmonad >>>> http://sinenomine.net >>>> >>> >>> >> >> _______________________________________________ >> xmonad mailing list >> xmonad at haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >> >> > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davama at gmail.com Thu Feb 2 13:46:10 2017 From: davama at gmail.com (Dave Macias) Date: Thu, 2 Feb 2017 08:46:10 -0500 Subject: [xmonad] Not inheriting default Keybindings Message-ID: Hello everyone been using xmonad for about 2 years now and it's great! something that was mention resently on another mail was something about "default keybindings being inherited or overwritten" That is actually what happens with my xmonad.hs. I have to manually code every default keybinding for them to work. It would be nice to shrink the xmonad.hs file by inheriting the default keybindings but i have no clue what to change. Im assuming my issue is in 'main' or 'defaults'. I tested mod+shift+enter which should run 'myTerminal' but it does not :( Here is a snippet of the config. Note that i pass 'hostname' down for perHost keybindings. http://pastebin.com/Msec53xJ Thank you for the assistance -dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From bodnarlajoska at gmail.com Sat Feb 4 15:54:42 2017 From: bodnarlajoska at gmail.com (Lajos Bodnar) Date: Sat, 4 Feb 2017 16:54:42 +0100 Subject: [xmonad] dual monitor In-Reply-To: References: Message-ID: Hi! Daniel, I tried the "IndependentScreens" and it's working like a charm. Thanks for all to all of you :) On Thu, Feb 2, 2017 at 8:17 AM, Lajos Bodnar wrote: > Hi Daniel. > I'm in my workplace and I will look at it home. > > thanks > Lajos > > On Thu, Feb 2, 2017 at 7:24 AM, Daniel Wagner wrote: > >> Can you show the config you tried after following the greedyView FAQ? >> That really should fix the behavior you're describing. >> >> The second feature you describe can *also* be done, see: >> http://hackage.haskell.org/package/xmonad-contrib-0.12/docs/ >> XMonad-Layout-IndependentScreens.html >> >> ~d >> >> On Wed, Feb 1, 2017 at 9:57 PM, Lajos Bodnar >> wrote: >> >>> Hi! >>> Morning :) >>> I tried what Brandon mentioned before, but the result is same. >>> Did you send me a correct link about a correct xmonad.hs ? >>> Maybe can I make a configuration where the half of the workspaces >>> resides the screen 1 and the other ones resides screen 2 ? >>> >>> Regards, >>> Lajos >>> >>> >>> On Wed, Feb 1, 2017 at 10:27 PM, Lajos Bodnar >>> wrote: >>> >>>> Thanks for the answers, I will check what Brandon mentioned. >>>> >>>> On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery >>>> wrote: >>>> >>>>> You don't need to add keybindings, they are default. I assume this >>>>> means you have been using the bad "example config" that overrides every >>>>> possible setting with the defaults from some particular version instead of >>>>> inheriting the defaults, and will need to be extremely careful about xmonad >>>>> upgrades because your config won't magically rewrite itself to be >>>>> compatible. (I think mod-shift-space is the one that will bite you in 0.13.) >>>>> >>>>> I *think* you are talking about https://wiki.haskell.org >>>>> /Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view >>>>> >>>>> On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar >>>> > wrote: >>>>> >>>>>> Hi all. >>>>>> I'm new in the mail list, and sorry for my english ... >>>>>> >>>>>> I tried to set up my wm for dual monitor with these keyboard settings: >>>>>> -- mod-[1..9], Switch to workspace N >>>>>> -- mod-shift-[1..9], Move client to workspace N >>>>>> -- >>>>>> [((m .|. mod4Mask, k), windows $ f i) >>>>>> | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] >>>>>> , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] >>>>>> ++ >>>>>> -- >>>>>> -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 >>>>>> -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 >>>>>> -- >>>>>> [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust >>>>>> (windows . f)) >>>>>> | (key, sc) <- zip [xK_w, xK_e] [0..] >>>>>> , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]] >>>>>> >>>>>> I exprerienced that when I switch workspace the opened windows moved >>>>>> the new workspace from the inactive screen. If the inactive screen is empty >>>>>> in the workspace where I have just moved then a window will fill it. I hope >>>>>> it is understandable for you. >>>>>> Any idea ? >>>>>> What is wrong ? What causes it ? >>>>>> >>>>>> Regards, >>>>>> Lajos >>>>>> >>>>>> _______________________________________________ >>>>>> xmonad mailing list >>>>>> xmonad at haskell.org >>>>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> brandon s allbery kf8nh sine nomine >>>>> associates >>>>> allbery.b at gmail.com >>>>> ballbery at sinenomine.net >>>>> unix, openafs, kerberos, infrastructure, xmonad >>>>> http://sinenomine.net >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> xmonad mailing list >>> xmonad at haskell.org >>> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >>> >>> >> >> _______________________________________________ >> xmonad mailing list >> xmonad at haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan.sinitsyn at gmail.com Sun Feb 12 07:52:12 2017 From: bogdan.sinitsyn at gmail.com (Bogdan Sinitsyn) Date: Sun, 12 Feb 2017 10:52:12 +0300 Subject: [xmonad] Not inheriting default Keybindings In-Reply-To: References: Message-ID: <8131652f-4829-55e1-1ad1-9991da30b7ba@gmail.com> You could use X.U.EZConfig for extending default keybindings instead of making new ones. On 02/02/2017 04:46 PM, Dave Macias wrote: > Hello everyone > > been using xmonad for about 2 years now and it's great! > something that was mention resently on another mail was something about > "default keybindings being inherited or overwritten" > > That is actually what happens with my xmonad.hs. I have to manually code > every default keybinding for them to work. > > It would be nice to shrink the xmonad.hs file by inheriting the default > keybindings but i have no clue what to change. Im assuming my issue is > in 'main' or 'defaults'. I tested mod+shift+enter which should run > 'myTerminal' but it does not :( > > Here is a snippet of the config. Note that i pass 'hostname' down for > perHost keybindings. > > http://pastebin.com/Msec53xJ > > Thank you for the assistance > > -dave > > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > -- Bogdan Sinitsyn From davama at gmail.com Mon Feb 20 18:52:11 2017 From: davama at gmail.com (Dave Macias) Date: Mon, 20 Feb 2017 13:52:11 -0500 Subject: [xmonad] Not inheriting default Keybindings In-Reply-To: <8131652f-4829-55e1-1ad1-9991da30b7ba@gmail.com> References: <8131652f-4829-55e1-1ad1-9991da30b7ba@gmail.com> Message-ID: After much trial and error i was able to implement Thanks for the tip! -dave On Sun, Feb 12, 2017 at 2:52 AM, Bogdan Sinitsyn wrote: > You could use X.U.EZConfig for extending default keybindings instead of > making new ones. > > > On 02/02/2017 04:46 PM, Dave Macias wrote: > >> Hello everyone >> >> been using xmonad for about 2 years now and it's great! >> something that was mention resently on another mail was something about >> "default keybindings being inherited or overwritten" >> >> That is actually what happens with my xmonad.hs. I have to manually code >> every default keybinding for them to work. >> >> It would be nice to shrink the xmonad.hs file by inheriting the default >> keybindings but i have no clue what to change. Im assuming my issue is >> in 'main' or 'defaults'. I tested mod+shift+enter which should run >> 'myTerminal' but it does not :( >> >> Here is a snippet of the config. Note that i pass 'hostname' down for >> perHost keybindings. >> >> http://pastebin.com/Msec53xJ >> >> Thank you for the assistance >> >> -dave >> >> >> _______________________________________________ >> xmonad mailing list >> xmonad at haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >> >> > -- > Bogdan Sinitsyn > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexsu04 at gmail.com Thu Feb 23 15:19:18 2017 From: alexsu04 at gmail.com (alexsu04 at gmail.com) Date: Thu, 23 Feb 2017 09:19:18 -0600 Subject: [xmonad] Cycle through all visible windows Message-ID: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> Hi all, I’ve been trying to get XMonad set up for dual monitor, but have been struggling with finding a way to cycle focus through every window (not workspace) visible on either screen. The behavior would be similar to XMonad.Actions.WindowNavigation (the experimental module), but the cycling wouldn’t be bound to any direction, just cycle through all visible windows in the normal Alt-Tab sequence (left to right, top to bottom). I’ve found some code in a previous thread that supposedly manipulates the StackSet, but it didn’t work for me: > -- top of config > import qualified XMonad.StackSet as W > -- somewhere at top level > onAllWS f = windows $ \ws at W.StackSet{ W.current = c, W.visible = vs } -> > let screenNext x = W.current . f $ ws { W.current = x } > c':vs' = map screenNext (c:vs) > in ws{ W.current = c', W.visible = vs' } ... > -- in keybindings: there are much more W.swap* W.focus* and W.shift* functions to use. > ,((modm, xK_f), onAllWS W.focusDown) > ,((modm, xK_d), onAllWS W.focusUp) > ,((modm, xK_g), onAllWS W.swapMaster) Unfortunately, I’m still too terrible at Haskell to fix whatever is wrong with the above code, and haven’t found any other modules that have the functionality I want. Any help would be appreciated! Thanks! Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From linusarver at gmail.com Thu Feb 23 19:49:09 2017 From: linusarver at gmail.com (Linus Arver) Date: Thu, 23 Feb 2017 11:49:09 -0800 Subject: [xmonad] Cycle through all visible windows In-Reply-To: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> Message-ID: <20170223194909.GA10827@larver-w0> On Thu, Feb 23, 2017 at 09:19:18AM -0600, alexsu04 at gmail.com wrote: > > Hi all, > > I’ve been trying to get XMonad set up for dual monitor, but have been struggling with finding a way to cycle focus through every window (not workspace) visible on either screen. The behavior would be similar to XMonad.Actions.WindowNavigation (the experimental module), but the cycling wouldn’t be bound to any direction, just cycle through all visible windows in the normal Alt-Tab sequence (left to right, top to bottom). > > I’ve found some code in a previous thread that supposedly manipulates the StackSet, but it didn’t work for me: > > > -- top of config > > import qualified XMonad.StackSet as W > > > -- somewhere at top level > > onAllWS f = windows $ \ws at W.StackSet{ W.current = c, W.visible = vs } -> > > let screenNext x = W.current . f $ ws { W.current = x } > > c':vs' = map screenNext (c:vs) > > in ws{ W.current = c', W.visible = vs' } > > ... > > > -- in keybindings: there are much more W.swap* W.focus* and W.shift* functions to use. > > ,((modm, xK_f), onAllWS W.focusDown) > > ,((modm, xK_d), onAllWS W.focusUp) > > ,((modm, xK_g), onAllWS W.swapMaster) > > > Unfortunately, I’m still too terrible at Haskell to fix whatever is wrong with the above code, and haven’t found any other modules that have the functionality I want. Any help would be appreciated! Have you looked at XMonad.Actions.CycleWS? I use it to cycle through all workspaces with windows in them. My config is customized beyond the standard XMonad config so you'd have to adapt it to your needs: https://github.com/listx/syscfg/blob/master/xmonad/xmonad.hs#L150 Another alternative might be XMonad.Actions.GridSelect as it gives you a popup of all open windows (not workspaces). Best, Linus > > Thanks! > > Alex > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad From alexsu04 at gmail.com Thu Feb 23 20:14:46 2017 From: alexsu04 at gmail.com (Alex Su) Date: Thu, 23 Feb 2017 14:14:46 -0600 Subject: [xmonad] Cycle through all visible windows In-Reply-To: <20170223194909.GA10827@larver-w0> References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <20170223194909.GA10827@larver-w0> Message-ID: Thanks for the response! Cycling through workspaces and then cycling focus isn't exactly what I was looking for, neither is GridSelect. Ideally, the behavior would be just be to move the currently focused window to the next window on any visible screen and cycle through (changing workspaces as necessary), whereas right now Alt-Tab is limited to cycling focus through windows on the focused workspace. There wouldn't be any screen swapping, just basically being able to Alt-Tab across the two physical screens that I have. On Thu, Feb 23, 2017 at 1:49 PM, Linus Arver wrote: > On Thu, Feb 23, 2017 at 09:19:18AM -0600, alexsu04 at gmail.com wrote: > > > > Hi all, > > > > I’ve been trying to get XMonad set up for dual monitor, but have been > struggling with finding a way to cycle focus through every window (not > workspace) visible on either screen. The behavior would be similar to > XMonad.Actions.WindowNavigation (the experimental module), but the > cycling wouldn’t be bound to any direction, just cycle through all visible > windows in the normal Alt-Tab sequence (left to right, top to bottom). > > > > I’ve found some code in a previous thread that supposedly manipulates > the StackSet, but it didn’t work for me: > > > > > -- top of config > > > import qualified XMonad.StackSet as W > > > > > -- somewhere at top level > > > onAllWS f = windows $ \ws at W.StackSet{ W.current = c, W.visible = vs } > -> > > > let screenNext x = W.current . f $ ws { W.current = x } > > > c':vs' = map screenNext (c:vs) > > > in ws{ W.current = c', W.visible = vs' } > > > > ... > > > > > -- in keybindings: there are much more W.swap* W.focus* and W.shift* > functions to use. > > > ,((modm, xK_f), onAllWS W.focusDown) > > > ,((modm, xK_d), onAllWS W.focusUp) > > > ,((modm, xK_g), onAllWS W.swapMaster) > > > > > > Unfortunately, I’m still too terrible at Haskell to fix whatever is > wrong with the above code, and haven’t found any other modules that have > the functionality I want. Any help would be appreciated! > > Have you looked at XMonad.Actions.CycleWS? I use it to cycle through all > workspaces with windows in them. My config is customized beyond the > standard XMonad config so you'd have to adapt it to your needs: > https://github.com/listx/syscfg/blob/master/xmonad/xmonad.hs#L150 > > Another alternative might be XMonad.Actions.GridSelect as it gives you a > popup of all open windows (not workspaces). > > Best, > Linus > > > > > Thanks! > > > > Alex > > > _______________________________________________ > > xmonad mailing list > > xmonad at haskell.org > > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlists at pmade.com Thu Feb 23 20:23:49 2017 From: mlists at pmade.com (Peter Jones) Date: Thu, 23 Feb 2017 13:23:49 -0700 Subject: [xmonad] Cycle through all visible windows References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <20170223194909.GA10827@larver-w0> Message-ID: <8760k0y7u2.fsf@pmade.com> Alex Su writes: > Thanks for the response! > > Cycling through workspaces and then cycling focus isn't exactly what I was > looking for, neither is GridSelect. Ideally, the behavior would be just be > to move the currently focused window to the next window on any visible > screen and cycle through (changing workspaces as necessary), whereas right > now Alt-Tab is limited to cycling focus through windows on the focused > workspace. There wouldn't be any screen swapping, just basically being able > to Alt-Tab across the two physical screens that I have. I think you want to bind Alt-Tab to `windowGo` from XMonad.Actions.Navigation2D: https://hackage.haskell.org/package/xmonad-contrib-0.13/docs/XMonad-Actions-Navigation2D.html -- Peter Jones, Founder, Devalot.com Defending the honor of good code From sua at uchicago.edu Thu Feb 23 20:30:52 2017 From: sua at uchicago.edu (Alex Su) Date: Thu, 23 Feb 2017 14:30:52 -0600 Subject: [xmonad] Cycle through all visible windows In-Reply-To: <8760k0y7u2.fsf@pmade.com> References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <20170223194909.GA10827@larver-w0> <8760k0y7u2.fsf@pmade.com> Message-ID: Correct me if I am wrong, but it looks to me like the windowGo function accepts also a directional input. I think I've tried that module, but whenever I have the case that I have a window to the left, then windows stacked on top of each other, then another window on the next screen over, just binding Alt-Tab to windowGo L for instance skips certain windows in the cycle, in this case the window on the first screen that is stacked under another. On Thu, Feb 23, 2017 at 2:23 PM, Peter Jones wrote: > Alex Su writes: > > Thanks for the response! > > > > Cycling through workspaces and then cycling focus isn't exactly what I > was > > looking for, neither is GridSelect. Ideally, the behavior would be just > be > > to move the currently focused window to the next window on any visible > > screen and cycle through (changing workspaces as necessary), whereas > right > > now Alt-Tab is limited to cycling focus through windows on the focused > > workspace. There wouldn't be any screen swapping, just basically being > able > > to Alt-Tab across the two physical screens that I have. > > > I think you want to bind Alt-Tab to `windowGo` from > XMonad.Actions.Navigation2D: > > https://hackage.haskell.org/package/xmonad-contrib-0.13/ > docs/XMonad-Actions-Navigation2D.html > > -- > Peter Jones, Founder, Devalot.com > Defending the honor of good code > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlists at pmade.com Thu Feb 23 21:03:33 2017 From: mlists at pmade.com (Peter Jones) Date: Thu, 23 Feb 2017 14:03:33 -0700 Subject: [xmonad] Cycle through all visible windows References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <20170223194909.GA10827@larver-w0> <8760k0y7u2.fsf@pmade.com> Message-ID: <87r32owrfe.fsf@pmade.com> Alex Su writes: > Correct me if I am wrong, but it looks to me like the windowGo function > accepts also a directional input. > > I think I've tried that module, but whenever I have the case that I have a > window to the left, then windows stacked on top of each other, then another > window on the next screen over, just binding Alt-Tab to windowGo L for > instance skips certain windows in the cycle, in this case the window on the > first screen that is stacked under another. Correct. `windowGo` won't help you if you have windows stacked on top of one another. Assuming you are talking about floating layers, you'd have to use something like `switchLayer` first before `windowGo`. Another thing to consider as an alternative is: https://hackage.haskell.org/package/xmonad-contrib-0.13/docs/XMonad-Prompt-Window.html -- Peter Jones, Founder, Devalot.com Defending the honor of good code From sua at uchicago.edu Thu Feb 23 21:15:34 2017 From: sua at uchicago.edu (Alex Su) Date: Thu, 23 Feb 2017 15:15:34 -0600 Subject: [xmonad] Cycle through all visible windows In-Reply-To: <87r32owrfe.fsf@pmade.com> References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <20170223194909.GA10827@larver-w0> <8760k0y7u2.fsf@pmade.com> <87r32owrfe.fsf@pmade.com> Message-ID: No the windows are in the same layer and not floating. They are tiled, but just split the screen in half top and bottom in the right half of the screen (I'm using the default Tall layout). Xprompt would be okay, but I was hoping someone might know about how to come up with a StackSet hack similar to the code in my first post that would work, or be able to point out what was wrong with it. I'm a little surprised that there's no module that supports this already... Thanks for your help so far though! On Thu, Feb 23, 2017 at 3:03 PM, Peter Jones wrote: > Alex Su writes: > > Correct me if I am wrong, but it looks to me like the windowGo function > > accepts also a directional input. > > > > I think I've tried that module, but whenever I have the case that I have > a > > window to the left, then windows stacked on top of each other, then > another > > window on the next screen over, just binding Alt-Tab to windowGo L for > > instance skips certain windows in the cycle, in this case the window on > the > > first screen that is stacked under another. > > Correct. `windowGo` won't help you if you have windows stacked on top > of one another. Assuming you are talking about floating layers, you'd > have to use something like `switchLayer` first before `windowGo`. > > Another thing to consider as an alternative is: > > https://hackage.haskell.org/package/xmonad-contrib-0.13/ > docs/XMonad-Prompt-Window.html > > -- > Peter Jones, Founder, Devalot.com > Defending the honor of good code > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlists at pmade.com Thu Feb 23 21:34:13 2017 From: mlists at pmade.com (Peter Jones) Date: Thu, 23 Feb 2017 14:34:13 -0700 Subject: [xmonad] Cycle through all visible windows References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> Message-ID: <87mvdcwq0a.fsf@pmade.com> writes: > I’ve been trying to get XMonad set up for dual monitor, but have been > struggling with finding a way to cycle focus through every window (not > workspace) visible on either screen. The behavior would be similar to > XMonad.Actions.WindowNavigation (the experimental module), but the > cycling wouldn’t be bound to any direction, just cycle through all > visible windows in the normal Alt-Tab sequence (left to right, top to > bottom). > > I’ve found some code in a previous thread that supposedly manipulates > the StackSet, but it didn’t work for me: > >> -- top of config >> import qualified XMonad.StackSet as W > >> -- somewhere at top level >> onAllWS f = windows $ \ws at W.StackSet{ W.current = c, W.visible = vs } -> >> let screenNext x = W.current . f $ ws { W.current = x } >> c':vs' = map screenNext (c:vs) >> in ws{ W.current = c', W.visible = vs' } > > ... > >> -- in keybindings: there are much more W.swap* W.focus* and W.shift* functions to use. >> ,((modm, xK_f), onAllWS W.focusDown) >> ,((modm, xK_d), onAllWS W.focusUp) >> ,((modm, xK_g), onAllWS W.swapMaster) Okay, let's start again. Why doesn't the code above work? Does it fail to compile or just fail to work the way you expect? If it fails to compile, what error messages are you getting from the compiler? -- Peter Jones, Founder, Devalot.com Defending the honor of good code From sua at uchicago.edu Thu Feb 23 21:46:45 2017 From: sua at uchicago.edu (Alex Su) Date: Thu, 23 Feb 2017 15:46:45 -0600 Subject: [xmonad] Cycle through all visible windows In-Reply-To: <87mvdcwq0a.fsf@pmade.com> References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <87mvdcwq0a.fsf@pmade.com> Message-ID: The code compiles fine, just doesn't do what I expect, so no error messages. >From what I can gather, the W.focus* functions take a StackSet and outputs another StackSet, which is then passed to the windows function to actually perform the action. My understanding is that onAllWS is supposed to modify the StackSet somehow to enable Alt-Tabbing across all windows on visible screens; beyond that my Haskell is a little too elementary to understand what is happening. On Thu, Feb 23, 2017 at 3:34 PM, Peter Jones wrote: > writes: > > I’ve been trying to get XMonad set up for dual monitor, but have been > > struggling with finding a way to cycle focus through every window (not > > workspace) visible on either screen. The behavior would be similar to > > XMonad.Actions.WindowNavigation (the experimental module), but the > > cycling wouldn’t be bound to any direction, just cycle through all > > visible windows in the normal Alt-Tab sequence (left to right, top to > > bottom). > > > > I’ve found some code in a previous thread that supposedly manipulates > > the StackSet, but it didn’t work for me: > > > >> -- top of config > >> import qualified XMonad.StackSet as W > > > >> -- somewhere at top level > >> onAllWS f = windows $ \ws at W.StackSet{ W.current = c, W.visible = vs } > -> > >> let screenNext x = W.current . f $ ws { W.current = x } > >> c':vs' = map screenNext (c:vs) > >> in ws{ W.current = c', W.visible = vs' } > > > > ... > > > >> -- in keybindings: there are much more W.swap* W.focus* and W.shift* > functions to use. > >> ,((modm, xK_f), onAllWS W.focusDown) > >> ,((modm, xK_d), onAllWS W.focusUp) > >> ,((modm, xK_g), onAllWS W.swapMaster) > > Okay, let's start again. > > Why doesn't the code above work? Does it fail to compile or just fail > to work the way you expect? If it fails to compile, what error messages > are you getting from the compiler? > > > -- > Peter Jones, Founder, Devalot.com > Defending the honor of good code > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Thu Feb 23 21:55:57 2017 From: allbery.b at gmail.com (Brandon Allbery) Date: Thu, 23 Feb 2017 16:55:57 -0500 Subject: [xmonad] Cycle through all visible windows In-Reply-To: References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <87mvdcwq0a.fsf@pmade.com> Message-ID: On Thu, Feb 23, 2017 at 4:46 PM, Alex Su wrote: > My understanding is that onAllWS is supposed to modify the StackSet > somehow to enable Alt-Tabbing across all windows on visible screens; beyond > that my Haskell is a little too elementary to understand what is happening. The code you show runs a single action across the workspaces on all screens. `onAllWS W.focusDown` would switch the focus on all visible workspaces, otherwise leaving you where you were. This is not the droid you're looking for.... -- brandon s allbery kf8nh sine nomine associates allbery.b at gmail.com ballbery at sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From sua at uchicago.edu Thu Feb 23 22:02:25 2017 From: sua at uchicago.edu (Alex Su) Date: Thu, 23 Feb 2017 16:02:25 -0600 Subject: [xmonad] Cycle through all visible windows In-Reply-To: References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <87mvdcwq0a.fsf@pmade.com> Message-ID: Any ideas about a more suitable droid? On Thu, Feb 23, 2017 at 3:55 PM, Brandon Allbery wrote: > > On Thu, Feb 23, 2017 at 4:46 PM, Alex Su wrote: > >> My understanding is that onAllWS is supposed to modify the StackSet >> somehow to enable Alt-Tabbing across all windows on visible screens; beyond >> that my Haskell is a little too elementary to understand what is happening. > > > The code you show runs a single action across the workspaces on all > screens. `onAllWS W.focusDown` would switch the focus on all visible > workspaces, otherwise leaving you where you were. This is not the droid > you're looking for.... > > -- > brandon s allbery kf8nh sine nomine > associates > allbery.b at gmail.com > ballbery at sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Thu Feb 23 22:06:16 2017 From: allbery.b at gmail.com (Brandon Allbery) Date: Thu, 23 Feb 2017 17:06:16 -0500 Subject: [xmonad] Cycle through all visible windows In-Reply-To: References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <87mvdcwq0a.fsf@pmade.com> Message-ID: Not really; I know more about workspace cycling. Don't even use alt-tab... but I think focus cycling across workspaces like that will be difficult given how focused the core is on stacks (which are part of a single workspace). On Thu, Feb 23, 2017 at 5:02 PM, Alex Su wrote: > Any ideas about a more suitable droid? > > On Thu, Feb 23, 2017 at 3:55 PM, Brandon Allbery > wrote: > >> >> On Thu, Feb 23, 2017 at 4:46 PM, Alex Su wrote: >> >>> My understanding is that onAllWS is supposed to modify the StackSet >>> somehow to enable Alt-Tabbing across all windows on visible screens; beyond >>> that my Haskell is a little too elementary to understand what is happening. >> >> >> The code you show runs a single action across the workspaces on all >> screens. `onAllWS W.focusDown` would switch the focus on all visible >> workspaces, otherwise leaving you where you were. This is not the droid >> you're looking for.... >> >> -- >> brandon s allbery kf8nh sine nomine >> associates >> allbery.b at gmail.com >> ballbery at sinenomine.net >> unix, openafs, kerberos, infrastructure, xmonad >> http://sinenomine.net >> > > -- brandon s allbery kf8nh sine nomine associates allbery.b at gmail.com ballbery at sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From sua at uchicago.edu Thu Feb 23 22:10:06 2017 From: sua at uchicago.edu (Alex Su) Date: Thu, 23 Feb 2017 16:10:06 -0600 Subject: [xmonad] Cycle through all visible windows In-Reply-To: References: <58aefd76.d0826b0a.c0849.8c0e@mx.google.com> <87mvdcwq0a.fsf@pmade.com> Message-ID: Hmm okay. I wonder how Windows.Actions.Navigate2D does it...maybe there's some way to copy their implementation and just get rid of the directional part; guess it's time for me to learn Haskell properly. Thanks! On Thu, Feb 23, 2017 at 4:06 PM, Brandon Allbery wrote: > Not really; I know more about workspace cycling. Don't even use alt-tab... > but I think focus cycling across workspaces like that will be difficult > given how focused the core is on stacks (which are part of a single > workspace). > > On Thu, Feb 23, 2017 at 5:02 PM, Alex Su wrote: > >> Any ideas about a more suitable droid? >> >> On Thu, Feb 23, 2017 at 3:55 PM, Brandon Allbery >> wrote: >> >>> >>> On Thu, Feb 23, 2017 at 4:46 PM, Alex Su wrote: >>> >>>> My understanding is that onAllWS is supposed to modify the StackSet >>>> somehow to enable Alt-Tabbing across all windows on visible screens; beyond >>>> that my Haskell is a little too elementary to understand what is happening. >>> >>> >>> The code you show runs a single action across the workspaces on all >>> screens. `onAllWS W.focusDown` would switch the focus on all visible >>> workspaces, otherwise leaving you where you were. This is not the droid >>> you're looking for.... >>> >>> -- >>> brandon s allbery kf8nh sine nomine >>> associates >>> allbery.b at gmail.com >>> ballbery at sinenomine.net >>> unix, openafs, kerberos, infrastructure, xmonad >>> http://sinenomine.net >>> >> >> > > > -- > brandon s allbery kf8nh sine nomine > associates > allbery.b at gmail.com > ballbery at sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: