Re: State of the X clipboard, and perhaps a solution

[Jerry Haltom <wasabi larvalstage net>]

You mean such as Evolution or something closing, but not exiting cleanly
in the background? These are bugs that should be addressed in there
respective programs. I've had this happen before.

If, using my idea for example, Gnumeric was closed, and a new Gnumeric
was started, the Gnumeric developers could decide how they would want to
handle that. A decent approach for perhaps a program smaller than
gnumeric (hehe) would be to spawn a second instance... and leave the
first instance in a "ready to die" state. After all, the first instance
has no point in existing other than to hold the clipboard contents. It
should have already closed open files, and other resources that might
prevent another process from starting, and if it hasn't, that's a bug.
Another way would be to not close Gnumeric, and use a remote type
command to launch a new window in the old process... which might already
be happening.



Quoting because message didn't go to ML:

On Fri, 2004-04-23 at 12:21 +1200, John Williams wrote:
> 
> IMHO as a user (not an active programmer) this point is a killer.  Many,
> many times I have experienced an otherwise inexplicable problem with my
> desktop interaction that I finally traced to a process that had not
> exited properly.  
> 
> Thank you for attempting to address the clipboard issue.  As you say, it
> really needs fixing.  However I really think that making program
> shutdown "non-deterministic" is too much to pay for this solution.
> 
> But don't let me discourage you from persevering! :-)
> 
> Cheers,
> 
> John
> 
> -- 
> ICQ: 261810463
> AIM: johnfrombluff
> AOL: johnfrombluff
> MSN: johnwilliamsFromBluff hotmail com
> Yahoo: JohnFromBluff
> Jabber: jwilliamsFromBluff jabber org
>