🚀 go-pugleaf

When I'm in my Calendar and type q (exit-calendar), the window which
ends up current gets its point zapped to start-of-buffer, regardless of
where it was before.  I imagine this arises in some way from the
window-configuration commands, which I don't claim to follow; as far as
I can make out, calendar-window-configuration gets set to the
configuration of my windows (in my principal frame) at the point where I
first invoke the calendar -- which is at startup, when the other window
(which takes up the portion of the frame that's not taken up by
calendar) is positioned at its top (because it's just been created).

Is there any way to get current-window-configuration to return an answer
which, when passed to set-window-configuration, will only affect the
positions of point and mark in the calendar/diary/holiday windows ?
Alternatively, is it really necessary to reset the window configuration
when exiting the calendar ?  Wouldn't it suffice to perform the given
actions on the calendar/diary/holiday windows and leave everything else
alone ?

	Eddy.