Absolutely. I am okay with creating a better tool using Python for example, but the competing project took the entire idea of a bash script on the local folder that implements plugins like my project.
Small details like the colors are the same on the colors script. I was referring to the fact that all those changes could have been done on the original project through Pull Requests, instead of dividing the effort.
>but the competing project took the entire idea of a bash script on the local folder that implements plugins like my project.
Ideas don't belong to anyone, though. And I'm sure you're not the first or only person to come up with "a bash script on the local folder that implements plugins". And unless you've got a patent on that, you've got no right to be upset that someone else does something you did first.
And again, you know, you did open source the code, which implies you want people to use your code and modify it if they wish.
But did they actually fork your project and not provide you credit? Your original comment made it seem as if they did, but now it appears you're just upset that someone else created a similar project to yours, rather than contribute to you.
If that's the case, it's understandable that you would rather they contribute to your project than have their own, but it's not plagiarism on their part. Contributions are a privilege, but forking is a right as far as open source is concerned.
The idea of using a bash script is not original. People have been writing custom bash scripts since about 1989. Why does it matter that the project was written in the same language if the argument is that they've copied your idea?
As for the specific colors, many people use those color choices when designing a CLI.
Small details like the colors are the same on the colors script. I was referring to the fact that all those changes could have been done on the original project through Pull Requests, instead of dividing the effort.