GIMP Version: 2.8.14
Operating System: Linux
OS Version: Debian 12 + Lxde (desktop)
GIMP Experience: New User

---

cd /home/debian/.local/share/gegl-0.4/plug-ins
ls
'*' gegleffects.so outlinedeluxe.so

file "*"
*: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=609bb39c6012e3b6d828b5a3c24296026e7772a0, not stripped

Why name the file "*" ?Wildcards are special characters that can be used to represent one or more characters in a filename. The most common wildcards in Linux are: * : Matches any number of characters (including zero characters).Does the file "*" harm my PC?

On Linux the only forbidden characters in filenames are "/" and the NULL.

This is probably a user error somewhere. When you specify a pattern as a parameter in a shell command, and the pattern doesn't match anything, the pattern is passed as is to the command(*), which uses it as a file name. Which is why "ls *foobar*" elicits "ls: cannot access '*foobar*': No such file or directory". If you do "cp somefile somedir/*", and there is no file in "somedir" yet, cp gets "somedir/*" as a second arg, uses it directly (file pattern expansion is only done by the shell) and you end up with a file "*" in "somedir".

(*) unless you have set the "nullglob" option in which case the argument is removed.

You can very likely erase the file without ill effects, just quote the name to avoid the file pattern substitution (or erase from your file explorer)

There is no `*` name shipped with my plugins. Never was and never has been.

Where did you get that * named file?

You made a mistake moving my plugins in the CLI and accidentally typed something that made a `*` file


I have never shipped that. I know there is a command like `mv *.so receiving_folder` so perhaps a mistake of that did it.