First, this code from style.c generates a warning:
if (SID_GET_HAS_NAME(s_id) (fw-style_name == NULL
(matchWildcards(SID_GET_NAME(s_id), fw-class.res_class) == TRUE ||
matchWildcards(SID_GET_NAME(s_id), fw-class.res_name) == TRUE ||
On Tue, Apr 04, 2006 at 02:38:21AM +0400, Serge (gentoosiast) Koksharov wrote:
Good (day|morning|night) everyone,
During examination of FvwmM4 '--debug' option I decided to examine FVWM's
temporary file creation mechanism. Can you believe what I dig out:
In libs/System.c there is a
On Thu, Apr 06, 2006 at 11:13:03AM +0200, Dominik Vogt wrote:
First, this code from style.c generates a warning:
if (SID_GET_HAS_NAME(s_id) (fw-style_name == NULL
(matchWildcards(SID_GET_NAME(s_id), fw-class.res_class) == TRUE ||
On Thu, 6 Apr 2006, Dominik Vogt wrote:
On Thu, Apr 06, 2006 at 11:13:03AM +0200, Dominik Vogt wrote:
First, this code from style.c generates a warning:
if (SID_GET_HAS_NAME(s_id) (fw-style_name == NULL
(matchWildcards(SID_GET_NAME(s_id), fw-class.res_class) == TRUE ||
On Thu, Apr 06, 2006 at 11:42:17AM +0200, Viktor Griph wrote:
Just some conciderations: The manpage states that styles are search for in
a specific order. I really fail to see how this information is useful
while examining the logic, other than for the face that matchig early will
save some
On Thu, 6 Apr 2006, Dominik Vogt wrote:
On Thu, Apr 06, 2006 at 11:42:17AM +0200, Viktor Griph wrote:
Just some conciderations: The manpage states that styles are search for in
a specific order. I really fail to see how this information is useful
while examining the logic, other than for the
On Thu, Apr 06, 2006 at 12:13:17PM +0200, Viktor Griph wrote:
On Thu, 6 Apr 2006, Dominik Vogt wrote:
On Thu, Apr 06, 2006 at 11:42:17AM +0200, Viktor Griph wrote:
Just some conciderations: The manpage states that styles are search for in
a specific order. I really fail to see how this
On 06 Apr 2006 12:47:59 +0200, Dominik Vogt wrote:
On Thu, Apr 06, 2006 at 12:13:17PM +0200, Viktor Griph wrote:
On Thu, 6 Apr 2006, Dominik Vogt wrote:
Do you mean this text:
They are searched in the reverse order stated.
When two conflicting styles apply to the same window,
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: dane06/03/23 21:19:36
Modified files:
. : AUTHORS ChangeLog INSTALL.fvwm NEWS
bin: ChangeLog fvwm-config.1.in
fvwm-menu-headlines.1 fvwm-menu-headlines.in
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt06/04/06 04:08:29
Modified files:
. : ChangeLog NEWS
bin: ChangeLog
fvwm : style.c
libs : Fft.c System.c
Log message:
* Applied
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: griph 06/04/06 04:35:00
Modified files:
. : ChangeLog
fvwm : fvwm.1.in style.c
Log message:
* fix style_name matching (typo)
* update documentation of fvwmstyle resource to reflect
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: griph 06/04/04 17:17:53
Modified files:
. : AUTHORS ChangeLog NEWS
fvwm : add_window.c fvwm.1.in fvwm.h style.c
Log message:
* let fvwmstyle resource override style name selection.
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt06/04/06 04:57:37
Modified files:
. : ChangeLog
Log message:
* Removed conflict marker.
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt06/04/06 05:52:32
Modified files:
fvwm : fvwm.1.in
Log message:
* Clarified order of style parsing.
On 06Apr2006 12:58, mikhael goikhman [EMAIL PROTECTED] wrote:
| So, how about this:
|
| When two opposite style options are specified for the same window
| (like Sticky and Slippery), then the last specified option wins.
Please say opposing instead of opposite. Opposite suggests exact
On 07 Apr 2006 11:42:43 +1000, Cameron Simpson wrote:
On 06Apr2006 12:58, mikhael goikhman [EMAIL PROTECTED] wrote:
|
| When two opposite style options are specified for the same window
| (like Sticky and Slippery), then the last specified option wins.
Please say opposing instead of
16 matches
Mail list logo
