On 09/09/2010 18:02, Cecil C. wrote:

I use Gimp under Ubuntu 10.04. My question is fairly simple. I have been using Gimp since 2.0, and have copied scripts over from release to release. Usually, some of the copied scripts are broken when a new release is available, such as from 2.4 to 2.6. To date, I have not made the effort to remove the broken scripts.

When a script is broken, I find out by running the script and getting an error message, such as "Error: set!: unbound variable: screen-layer". I know how I invoked the script from the menu, so I can edit all the scripts in my directory to see where they put the script in the menu structure and the name they used. Often, I can narrow the number of scripts I have to edit to find the correct one by using the script name as a starting point. However, there are a significant number of scripts that have a different file name than that used in the menu. Needless to say, this is a tedious and slow process.

Is there an easier way to identify a broken script file other than the process I have outlined above?

I don't know what UI you use (Gone/KDE....), but a decent file navigator/browser should also have the tools to search files on content.

On Thu, 2010-09-09 at 18:02 +0200, Cecil C. wrote:

I use Gimp under Ubuntu 10.04. My question is fairly simple. I have been using Gimp since 2.0, and have copied scripts over from release to release. Usually, some of the copied scripts are broken when a new release is available, such as from 2.4 to 2.6. To date, I have not made the effort to remove the broken scripts.

When a script is broken, I find out by running the script and getting an error message, such as "Error: set!: unbound variable: screen-layer". I know how I invoked the script from the menu, so I can edit all the scripts in my directory to see where they put the script in the menu structure and the name they used. Often, I can narrow the number of scripts I have to edit to find the correct one by using the script name as a starting point. However, there are a significant number of scripts that have a different file name than that used in the menu. Needless to say, this is a tedious and slow process.

Is there an easier way to identify a broken script file other than the process I have outlined above?

Probably the easiest way to find a script that contains a certain string (as found in the error-message) is to use the grep utility. Try 'man grep'.

Sven

On Thu, 2010-09-09 at 18:02 +0200, Cecil C. wrote:

I use Gimp under Ubuntu 10.04. My question is fairly simple. I have been using Gimp since 2.0, and have copied scripts over from release to release.

Usually, some of the copied scripts are broken when a new release is available, such as from 2.4 to 2.6. To date, I have not made the effort

to

remove the broken scripts.

When a script is broken, I find out by running the script and getting an

error

message, such as "Error: set!: unbound variable: screen-layer". I know how

I

invoked the script from the menu, so I can edit all the scripts in my directory to see where they put the script in the menu structure and the

name

they used. Often, I can narrow the number of scripts I have to edit to

find

the correct one by using the script name as a starting point. However,

there

are a significant number of scripts that have a different file name than

that

used in the menu. Needless to say, this is a tedious and slow process.

Is there an easier way to identify a broken script file other than the

process

I have outlined above?

Probably the easiest way to find a script that contains a certain string (as found in the error-message) is to use the grep utility. Try 'man grep'.

Sven

Install "mc".
It is a very handy filebrowser.
Open it in a console.
Open your home directory and go to
/home//.gimp-2.6
Hit enter and then go to ~plug-ins and ~scripts.
You'll find python scripts in plug-ins and scm scripts in scripts. Put the cursor on the script you want to delete and hit F8. It might be wise to create a temporary directory somewhere and backup everything first.
Gerard.