I never heard back about this patch. Is it acceptable or do you want
me to make changes?
Thanks,
-Ross Combs
> From: "Requests for CTWM via RT" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Mon, 13 Mar 2006 06:55:27 +0100
>
>
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "CTWM man page corrections",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket has been
> assigned an ID of [repository.lp.se #116].
>
> Please include the string:
>
> [repository.lp.se #116]
>
> in the subject line of all future correspondence about this issue. To do so,
> you may reply to this message.
>
> Thank you,
> [EMAIL PROTECTED]
>
> -------------------------------------------------------------------------
> I maintain a version of tvtwm and I was reading through the
> CTWM man page about the OpaqueMove and OpaqueResize options
> (I have been trying to add CTWM rc-file compatibility.)
> when I noticed a couple of small errors.
>
> One is that the window list arguments for the opaque
> keywords are now optional, are listed with square brackets
> in the man page. The other is that the two Threshold
> keywords are shown in the man page as requiring curly-
> brackets, but they are not required or accepted in
> configuration files.
>
> I'm including the simple patch against version 3.7 below.
>
> Thanks,
> -Ross
>
>
> --- ctwm.man 2005-06-21 00:35:18.000000000 -0500
> +++ ctwm-fixed.man 2006-03-12 21:04:30.000000000 -0600
> @@ -1042,9 +1042,9 @@
> This variable indicates that menus should not have drop shadows drawn behind
> them. This is typically used with slower servers since it speeds up menu
> drawing at the expense of making the menu slightly harder to read.
> -.IP "\fBNoOpaqueMove\fP { \fIwindow\-list\fP }" 8
> +.IP "\fBNoOpaqueMove\fP [{ \fIwindow\-list\fP }]" 8
> The counterpart of \fBOpaqueMove\fP. See \fBOpaqueMove\fP.
> -.IP "\fBNoOpaqueResize\fP { \fIwindow\-list\fP }" 8
> +.IP "\fBNoOpaqueResize\fP [{ \fIwindow\-list\fP }]" 8
> The counterpart of \fBOpaqueResize\fP. See \fBOpaqueResize\fP.
> .IP "\fBNoRaiseOnDeiconify\fP" 8
> This variable indicates that windows that are deiconified should not be
> @@ -1134,7 +1134,7 @@
> .EE
> Note : The OccupyAll declaration should come after the WorkSpaces
> declaration.
>
> -.IP "\fBOpaqueMove\fP { \fIwindow\-list\fP }" 8
> +.IP "\fBOpaqueMove\fP [{ \fIwindow\-list\fP }]" 8
> This variable indicates that the \fBf.move\fP function should actually move
> the window instead of just an outline so that the user can immediately see
> what the window will look like in the new position. This option is typically
> @@ -1142,17 +1142,17 @@
> window list parameter indicates that only windows in this list should
> actually
> be moved in opaque mode. The \fBNoOpaqueMove\fP counterpart is also
> available.
>
> -.IP "\fBOpaqueMoveThreshold\fP { \fIthreshold\fP }" 8
> +.IP "\fBOpaqueMoveThreshold\fP \fIthreshold\fP" 8
> The integer parameter is a percentage and indicates that only windows
> (elligible
> for opaque moving) with a surface smaller than this percentage of the surface
> of the screen should actually be moved in opaque mode.
>
> -.IP "\fBOpaqueResize\fP { \fIwindow\-list\fP }" 8
> +.IP "\fBOpaqueResize\fP [{ \fIwindow\-list\fP }]" 8
> The opaque version of resize. Extremely resource intensive,
> but beautiful with fast server/client/network. See \fBOpaqueMove\fP. The
> \fBNoOpaqueResize\fP counterpart is also available.
>
> -.IP "\fBOpaqueResizeThreshold\fP { \fIthreshold\fP }" 8
> +.IP "\fBOpaqueResizeThreshold\fP \fIthreshold\fP" 8
> The resize version of \fBOpaqueMoveThreshold\fP.
>
> .IP "\fBOpenWindowTimeout\fP \fIseconds\fP" 8
>
>
