Custom perl to paste X CLIPBOARD stopped working

[rxvt-unicode at catcons.co.uk]

> ----------------------------------------------------------------------
> Date: Sun, 1 May 2011 09:21:45 -0700
> From: Chip Camden <sterling at camdensoftware.com>
> To: rxvt-unicode at lists.schmorp.de
> Subject: Re: Custom perl to paste X CLIPBOARD stopped working
> Message-ID: <20110501162144.GA72298 at libertas.local.camdensoftware.com>
> Content-Type: text/plain; charset="us-ascii"
[snip]
> I often just do a print and then by starting urxvt from a shell prompt
> you can see the print output in the parent shell.

> ------------------------------
> Date: Sun, 1 May 2011 19:47:54 -0400 (EDT)
> From: "Benjamin R. Haskell" <rxvt-unicode at benizi.com>
> To: rxvt-unicode at lists.schmorp.de
> Subject: Re: Custom perl to paste X CLIPBOARD stopped working
> Message-ID: <alpine.LNX.2.01.1105011938091.28316 at hp>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
[snip]
> As with most programs, you should put your own customizations 
> into your 
> own director(y|ies).  If you add:
> URxvt*perl-lib: /home/username/urxvt
> 
> You can put this in /home/username/urxvt/clipboard.

Thanks Chip and Ben :-)

The problem is solved, thanks to your suggestions.

It was a system update that had triggered the changed behaviour, a new
version of xrdb (1.0.9).  In ~/.Xresources, there was a trailing space after
URxvt.keysym.Mod4-v: perl:clipboard:paste.  Unusually I had not logged off
the night after the update.  I had a log from the following day showing that
paste was working -- as it continued to do until I logged off and on again
and the new xrdb parsed .Xresources.

The trailing space came to light when I modified ~/.Xresources to implement
Ben's good practice suggestion of keeping customisations in personal
directories -- and did a diff -u to record the change.

Thanks again for pointing me in the right direction to solve what could have
been a very difficult issue to identify and fix.

The apparently inconsistent logging behaviour was caused by my incompetent
perl errors in the logging code (not illustrated in the original message)
which were easy to see on changing from print to file to print to stdout.

Best

Charles