Fun with prawnsushi

[prawnsushi]

@Whatnot I Fixed Paper Cuts and just uploaded the file. It “should” work again if you update the filters.
dilate_circ doesn’t seem to accept float values anymore? I removed the command, filter should be a little faster now (or not).

I also fixed Sloppy Mess which errored out if you selected a width which resulted in a float value. A quick fix but i guess i should change how i use split. I think it was changed recently?

And now i have to find out why my stringify mod crashes too No idea yet.

[0;32;59m<gmic>./pr_stringify/*foreach/*local/*repeat/ Item[80]: '+sh[$p]' -> 'sh[3]', selection [3].e[0;0;0m
e[0;32;59m<gmic>./pr_stringify/*foreach/*local/*repeat/ Command 'sh': arguments = '+sh[3]'.e[0;0;0m
[gmic]./pr_stringify/*foreach/*local/*repeat/ Input file '+sh[3]' at position 3
[gmic]./pr_stringify/*foreach/*local/*repeat/ e[0;31;59me[1m*** Error *** Unknown command or filename '+sh[3]'; did you mean 'sh'?e[0;0;0m

@David_Tschumperle Do you have any idea why this would happen? I never modified your code in this part…

[Reptorian]

I don’t think sh/shared is supposed to use +? That’s my idea anyway. I never had a case where I need to do +sh.

[prawnsushi]

Well, removed the + and it actually worked
Strange thing is that +sh is in the original filter, and it actually works.
And it used to work in my version too, but not anymore?
Don’t ask me what’s happening there

[afre (Alan)]

I think the possibility of +sh was removed a one point. + might mean creating a copy of a sh buffer, but what would happen to the copy if one removes the original buffer?

[prawnsushi]

Don’t know, could have been a shortcut to copy a channel?
But,If David used it, that means it should still work…

[David_Tschumperle (G'MIC staff)]

@prawnsushi

Strange thing is that +sh is in the original filter, and it actually works.
And it used to work in my version too, but not anymore?

Yes. It’s actually the result of a major rewrite of parts of interpreter (relative to command parsing). Parsing rules have been strenghtened.
Now, some commands (as sh !) do not support to be called with a + prefix.
As sh already inserts a new image in the list, the + is unnecessary.

[prawnsushi]

Alright, that clears things up

[David_Tschumperle (G'MIC staff)]

Yes, to be honest I was a bit horrified when I got back into the interpreter parsing code, because it was actually possible to write very strange (but functionnal) things that didn’t really make sense, like +do, +window, things like that…
The new parsing code helped to normalize all this.

(note also that it’s not possible to define a custom command that would correspond to +do, which would be a quite silly idea ).

[David_Tschumperle (G'MIC staff)]

@Whatnot

I get an error that says:
*** Error *** Command ‘afre_contrast’: Undefined argument ‘$2’, in expression ‘$2’ (for 1 argument specified).

That’s something I can try to debug as well.

@afre

The filters are old in G’MIC time

From now on, G’MIC’s development will clearly slow down. As I wrote in the conclusion of my last news article, it is time for the project to stop developing/breaking stuffs, and instead enter a phase of consolidation and promotion of what already exists (which is clearly stable and solid enough).

That is at least my goal for the coming months, focusing mainly on maintenance, debugging for the code parts, and promotion to increase the project visibility.