[xmonad] auto start apps on login, but not reloads

Sam Halliday sam.halliday at gmail.com
Fri Mar 24 22:16:49 UTC 2017


Thanks Ondrej,

Do you have a fuller example of how you did that? I get lost in the Haskell.


On 24 March 2017 at 22:02, Ondřej Súkup <mimi.vx at gmail.com> wrote:
> hi,
>
> I using for this simple :
>
>      import XMonad.Util.SpawnOnce (spawnOnce)
>      and managehook with doShift
>
>
> On 24 March 2017 at 21:43, Sam Halliday <sam.halliday at gmail.com> wrote:
>> Hi Brandon,
>>
>> When I did an `xmonad --restart` it started all the apps again...
>> which is exactly the opposite of what I wanted. I only want the apps
>> to start on initial startup.
>>
>> Just thinking aloud, another way I could do this would be to have
>> rules in place that always assign a new app to a given workspace. Then
>> I could start my main apps as usual from .xsession. But sometimes I
>> move a chromium window to a different workspace, so it would need to
>> allow that.
>>
>> BTW, I'm using xmonad from ArchLinux 0.13. Should I be using a dev version?
>>
>>
>> On 24 March 2017 at 19:53, Brandon Allbery <allbery.b at gmail.com> wrote:
>>>
>>> On Fri, Mar 24, 2017 at 12:09 PM, Sam Halliday <sam.halliday at gmail.com>
>>> wrote:
>>>>
>>>> Thanks Brandon!
>>>>
>>>> I've updated my config
>>>>
>>>>   https://github.com/fommil/dotfiles/blob/master/xmonad/xmonad.hs
>>>>
>>>> and now my three apps startup on the correct workspaces! No apparent
>>>> issues with chromium.
>>>>
>>>> Unfortunately, this doesn't seem to have fixed the --reload problem, so
>>>> I guess args is always coming up non-null?
>>>
>>>
>>> Hm? Did it restart them inappropriately, or did it not start them at all?
>>>
>>> The recent changes to use a state file are buggy and cause some rather
>>> bizarre problems. But there's also the question of compatibility with older
>>> versions; I was reassured that the change *is* backward compatible, but if
>>> you aren't seeing parameters from a restart then either that or some other
>>> change is not backward compatible. (I've already had to rewire this once
>>> because of an unannounced non-backward-compatible change leading up to 0.12.
>>> I am not a fan of "move fast, break stuff" especially if the only way I can
>>> find out about it is to audit every single commit.)
>>>
>>> --
>>> 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


More information about the xmonad mailing list