Comment 13 for bug 769344

Let's just say that newline.py is a _very_ lightweight version of the network.py plugin - just a lot worse. It takes your last entry, appends \n to it and puts it back. grow.py seems to do a similar thing (it's what I called "extension" earlier). They stand a chance of locking up glipper as well (although I haven't seen them do this yet, and I don't know what the difference is). newline.py is probably not used by anyone, grow.py goes through the history rather than the clipboard, nopaste.py only reads the first entry of the history and posts it to a pastebin-like site and opens a browser with the link (it doesn't do that for me though, just reading the code about what it should do)... so not many chances of deadlocking glipper there.

There may be some secret sauce in "emit" which can cause the actual clipboard action to happen on the main thread instead of the emitting thread, explaining why I haven't seen deadlocks before (I always used grow.py) and that makes me wonder why is add_history_item going straight for the clipboards while all the others go through the history. I have to say I don't know Gobject either :) I only know a bit of Qt, and the concepts seem similar (just different programming language).

I'm on IRC on Freenode, channel #linuxmce-devel, my nick there is Uplink_ (with the underscore), but I do weird hours, so you never know if I'm around (for example, today I've been awake for 20 hours and I'd better get to bed). I can learn Bazaar from the documentation. Already committed the latest patch in my local branch, and if I'll start doing heavy work, I'll probably put a copy on Launchpad too. But right now I like the last patch the way it is :D - Which is quite good given the fact that I don't know anything about the language (Python) or the framework (Gobject, GTK, GDK) and it's the first time I dived into glipper code.