Linux

52777 readers

479 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Those who use DWM, how do you get the autostart scripts to work? (lemmy.world)

submitted 1 week ago by mazzilius_marsti@lemmy.world to c/linux@lemmy.ml

11 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] XTL@sopuli.xyz 3 points 1 week ago

It's not a file name. It's shell syntax. Specifically, https://en.wikipedia.org/wiki/Job_control_(Unix)

That's a pretty terrible article on the subject, but I don't have a better one at hand. You could read some shell scripting tutorial or manual or maybe a beginners guide to Unix. A decent one should explain job control well.

But basically, in a script or command line, an ampersand ends a command and runs it in the background without waiting for it to finish before running the next command. A semicolon works the same but waits on the foreground.