A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
When you edit your $PATH environment variable, you don't have to use quotes
$PATH
e.g. the following is perfectly valid
PATH=$PATH:/my/new/path/
I always thought you had to do the following, just in case $PATH expanded into something with a space, but it turns out it's fine either way
PATH="$PATH:/my/new/path/"
Whether quotes are needed in different languages is so inconsistent 😄
Some comments have been hidden by the post's author - find out more
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
Uniting blockchain builders and thinkers.
When you edit your
$PATHenvironment variable, you don't have to use quotese.g. the following is perfectly valid
I always thought you had to do the following, just in case $PATH expanded into something with a space, but it turns out it's fine either way
Whether quotes are needed in different languages is so inconsistent 😄