I’m talking about this patch:

https://dwm.suckless.org/patches/autostart/

Now, the notes seem simple: after apply the patch, dwm will look for the autostart script in ~/.dwm/autostart.sh.

But if you read it carefully, the file is:

~/.dwm/autostart.sh &

Wth does a “&” have to do with file name? I tried to just use the normal file: autostart.sh with exec dunst. It doesnt work…

I tried to create in the Thunar this weird file name, “autostop.sh &”. The system does not recognize it as sh script anymore. .

Any help is welcome.

  • gnuhaut@lemmy.ml
    1·
    9 days ago

    The file autostart.sh file needs to be executable. This might be why it’s not working.

  • vvv@programming.dev
    1·
    10 days ago

    The & is an indicator to most shells to run this command in “the background”. Try and run ( sleep 10; echo hi ) & - you’ll see you get your shell prompt back, where you can run more commands, but 10 second later you’ll see that ‘hi’ come through. ‘blocking’ is the default behavior, if you don’t add the & you’re still going get the hi in ten seconds, but you don’t get a prompt because your shell’s execution is blocked until your command is done.

    The doc here is indicating that you havea choice between autostart_blocking.sh and autostart.sh, the latter of which would be run with a &. They could have expressed this better.

    As for why your script didn’t work, I’d try executing it in a terminal to see what error message comes up.