Re: [Gimp-user] After Python plugin crashed, the plugin is not loaded anymore

[Ofnuts <ofnuts gmx com>]

On 27/12/16 23:19, GimpMin wrote:
> Hello Ofnuts,
>
> thank you for your reply. The hint with the startup info on the console helped a
> lot. As in most of these strange cases, the problem was in between keyboard and
> chair... ;-)
>
> My simple script didn't start, since I had an "Umlaut" in an comment of which I
> thought I had removed already.
>
> For the bigger script, I actually do not know the problem. Yesterday, when I
> tried it first, it was complaining about an indention problem, which I could not
> find, the given line was obviously ok. And, surprise, surprise, today, it does
> not complain. It seems that this is one of the issues programmers face
> sometimes...

Some indentation problems can be hard to find because your editor shows 
tabs as N spaces, while these are
different for Python. Since you are on Kubuntu, Kate will do it...

You can keep umlauts in comments if you add:

# -*- coding: utf-8 -*-

or

# -*- coding: iso-8859-15 -*-

.. as the second line in your file (and have the editor save the file 
with the proper encoding, and AFAIK Kate
will do so if it sees such indications).