Script-fu console.
> (atom->string 5 2)
Error: ( : 1) atom->string: needs 1 argument(s)

Gimp version 2.10.0+om-1ubu18.04.1~ppa from Otto Meier <otto@kesselgulasch.org>
Ubuntu 18.04 LTS (Bionic Beaver)

Gimp 2.10.1 AppImage.

I'm currently thinking that those of you where this is failing for two parameters to atom->string have a build of GIMP that hasn't been done cleanly as the tinyscheme code appears to have been changed during 2.10 development.

To judge from the code on main,
in the file root/plug-ins/script-fu/tinyscheme/opdefines.h atom->string is defined as accepting a minimum of 1 parameters and a maximum of 2

And the code for atom->string in root/plug-ins/script-fu/tinyscheme/scheme.c is allowing for 2 parameters.

So I think that the failing builds haven't updated their tinyscheme sufficiently recently.

> (number->string 5) //works in GIMP 2.8 though
Error: ( : 1) atom->string: needs 1 argument(s)

> (number->string 5 10)
Error: ( : 1) atom->string: needs 1 argument(s)

> (number->string 5 . 10)
Error: ( : 1) atom->string: needs 1 argument(s)

Gimp 2.10 flatpak on Linux Mint 18.3

These are my results.
Tried to find examples in the provided scripts ... but they have the same problem. i.e they look as not being transferred to GIMP 2.10

Well with the information you gave me I'll have to wait for an update of GIMP I guess.
Thanks a lot for helping me so far. I appreciate that.

Just tested gimp-2.10.0-RC1-20180327 AppImage
worked as expected!
> (number->string 5)
"5"
> (number->string 5 10)
"5"
> (number->string 5 16)
"5"
> (number->string 5 2)
"101"

Shouldn't we have a problem with old scripts at all?

Read this from one of the GIMP devs:


found here: http://www.gimpusers.com/forums/gimp-de ... ssage90016

Gimp 2.8


I guess that throws that theory out the window.

You demonstrated that there was a problem in GIMP 2.8 but my argument is that nelo's Flatpak has only got half the fix and other builds have got the full fix.

Could it be possible that GIMP-2.10-RC1 has the fix but Gimp-2.10 final has a broken TinyScheme?

looks like it .. at least to me as a non-developer

I'll go one further. Gimp 2.10-RC1 is more forgiving with poorly coded scripts. They tightened it up with the final release, so it won't run un-compliant scripts.

That's my un-qualified opinion anyway.

I just checked gimp/plug-ins/script-fu/tinyscheme/ on github. It looks like there has been no drastic work done on TinyScheme.
https://github.com/GNOME/gimp/tree/mast ... tinyscheme
Somebody just ran a spell-checker over a lot of Gimp files and fixed typos in comments.
That should have no effect.

I was able to fix my scrip-fu console.



What I did was delete the script-fu file in username/.config/GIMP/2.10/plug-ins/
It is <helpfully> carried-on by the Gimp 2.10 install and conflicts with the script-fu installed by Gimp 2.10 in /usr/lib/gimp/2.0/plug-ins/script-fu.
Just re-naming it wasn't enough. I had to delete it.

Indeed ... that worked for me, too !
Thanks for finding that.
Now we need a replacement for script-fu scrolling interface, don't we?

Awesome find Tas_mania! Works great here too....

As for scrolling, I just hold down the Ctrl key while moving the window up with the mouse.

What a trick! So easy.
Works on Linux Mint using Ctrl+Alt
Thanks a lot for posting

Actually, I was wrong about the key. I just need to hold down the Alt key and move the settings window with the mouse on my Linux Mint 18.3 and Gimp 2.10.1 AppImage.

The script I was testing worked perfectly after deleting the old script-fu.

I logged it as a bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=796263
That was an experience. Gimp bugzilla uses ancient software

I'm sure Gimp 2.10 imports plugins and scripts from old Gimp versions into the .config folder.
We'll see what happens........

In principle he's right. It doesn't come with GIMP natively. But we use it, because we need scrolling script-fu windows sometimes. And I wonder why the devs don't integrate scrolling when it's easily done by a simple plugin. I think there was even a feature request years ago ( can't find it at the moment).

"It doesn't come with GIMP natively".
Now I remember we needed it to scroll windows. No wonder you are using the keyboard again.

Maybe 3 of us had Gimp 2.9, then we installed Gimp 2.10 and the new Gimp picked-up our plugins from the 2.9 folder (which was also in /.config)

Either that or we copy and pasted our scripts and plugins into Gimp 2.10 from previous Gimps.
That means we caused the problem and my bug report was a waste of time.

Either way we found out what makes "Error: ( : 1) atom->string: needs 1 argument(s)" and it's here for others.