> >> Maybe a better solution would be specify a padding value. > > I can't see any way to determine a padding value that would always work, > given that the user can mess with the time format. It might be enough to > always suffix his time format with a space, I suppose. >
I can see a user (like you) who knows that his clock string grows by say 2 pixels could add something to his rc file that says "allocate 30 chars for my clock, trust me". However I would much rather find a way to get this right the first time and not need hacks like this. Will see what we can figure out.
