It would help if you give the version of linux you have installed such as Ubuntu 22.04 or Mint 21 or Debian 10 .... there are any number of linux's Then if that installation is anything different such as a linux in a chromebook for example.
Back to the question. That first bit /home/c in linux can be abbreviated to ~ (that is your home folder/partition)
So the best place to put your scripts is ~/.config/GIMP/2.10/scripts/ and the same for any of the other resources; plug-ins / fonts / brushes / ... there is a folder for each.
You can put them in the /usr/lib/gimp/2.0/share - for scripts / brushes / palettes but why make things difficult for yourself. The same for plug-ins /usr/lib/gimp/2.0/plug-ins/
For linux plugins, either binary or somename.py, these need to be executable. You can usually set that using the file browser, what you get depends on the linux version.
When it comes to python plugins, there can be a snag. The most recent linux does not support the python2 required for them. There are fixes but that is another story.
Lets start off with the version of linux you use. If you are not sure, in a terminal lsb_release -a might tell you.
Back to the question. That first bit /home/c in linux can be abbreviated to ~ (that is your home folder/partition)
So the best place to put your scripts is ~/.config/GIMP/2.10/scripts/ and the same for any of the other resources; plug-ins / fonts / brushes / ... there is a folder for each.
You can put them in the /usr/lib/gimp/2.0/share - for scripts / brushes / palettes but why make things difficult for yourself. The same for plug-ins /usr/lib/gimp/2.0/plug-ins/
For linux plugins, either binary or somename.py, these need to be executable. You can usually set that using the file browser, what you get depends on the linux version.
When it comes to python plugins, there can be a snag. The most recent linux does not support the python2 required for them. There are fixes but that is another story.
Lets start off with the version of linux you use. If you are not sure, in a terminal lsb_release -a might tell you.