Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
In my head I would expect that if you just use the name, it should search in cwd and then next priority would be path. Because the cwd is basically the context you're working in. That's why this trips me up every time, this design doesn't mesh well with my mental model.
But maybe that's a me thing.
Well, if you want it to do that, you can just add . to your PATH.
I would be very certain that you are not going to cause any collisions, though. Remember that shell scripts will inherit your PATH and may call things you aren't thinking about.