[Gimp-developer] Python back-up files

2008-09-27 Thread Samuel
Another question from me: When I write a plugin, my text editor (kwrite or kate) creates a backup file named plugin.py~. When I start now the plugin in GIMP, it is executing the backup instead the original. As a workaround I execute chmod -x *~ but sometimes I forget this and this is annoying.

Re: [Gimp-developer] Python back-up files

2008-09-27 Thread Chris Mohler
On Sat, Sep 27, 2008 at 6:16 PM, Samuel <[EMAIL PROTECTED]> wrote: > Another question from me: > > When I write a plugin, my text editor (kwrite or kate) creates a backup > file named plugin.py~. When I start now the plugin in GIMP, it is > executing the backup instead the original. Hi, I think y

Re: [Gimp-developer] Python back-up files

2008-09-27 Thread Joao S. O. Bueno
On Saturday 27 September 2008, Chris Mohler wrote: > On Sat, Sep 27, 2008 at 6:16 PM, Samuel <[EMAIL PROTECTED]> wrote: > > Another question from me: > > > > When I write a plugin, my text editor (kwrite or kate) creates a backup > > file named plugin.py~. When I start now the plugin in GIMP, it is

Re: [Gimp-developer] Python back-up files

2008-09-28 Thread gg
On Sun, 28 Sep 2008 02:21:13 +0200, Chris Mohler <[EMAIL PROTECTED]> wrote: > On Sat, Sep 27, 2008 at 6:16 PM, Samuel <[EMAIL PROTECTED]> wrote: >> Another question from me: >> >> When I write a plugin, my text editor (kwrite or kate) creates a backup >> file named plugin.py~. When I start now the