Re: Patch to allow multiple window names in conditions
> Next (Netscape konqueror Mozilla*) WarpToWindow 99 90 This is a nice implementation of an "OR" rule, is there any way of specifying and "AND" rule? For example, a rule to match a window with Class "Netscape" and Title "local*". Now that multiple window names can be read, why not include one. For example, i would want these to this expression All (Netscape) ThisWindow (local*) ... to be reduced to All (Netscape local*) But this is exactly the syntax used by this patch, hence it means "OR". By default, all other conditions must be true, so i propose an alternate syntax for window name/class/resource "OR" conditions: All (Netscape |konqueror |Mozilla*) ... Perhaps it's not worth the effort? I just thought it was a little counter-intuitive. This also works well with "not" commands: All (Netscape |konqueror |Mozilla* !Opera) ... will match all browsers except opera if "!Opera" is read as an "AND NOT" (which is subtly different to the patch syntax's implied "OR NOT") I guess one could implement an "OR NOT" rule, but i strongly doubt the usefulness of it. I'd imagine a _full_ implementation of this would require a linked list of linked lists so one can specify multiple OR conditions eg.: All (Netscape |konqueror http* |file* !http://www.google*) would match all netscape and konqueror windows with titles that start with either http or file but not showing google. Note the "not google" rule needn't be applied to a specific list as its evaluation to true anywhere negates the rule. But of course a simpler (perhaps better too) method would just implement: All (Netscape |konqueror |http |file !opera) Of course, these are all just suggestions :) Great patch though, - Craig -- [EMAIL PROTECTED] -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Patch to allow multiple window names in conditions
This is a small patch that allows multiple window names to be specified
in conditions. I've tried to write it with the same style used in the
rest of the code, although some variable names may be a bit terse by your
standards. The patch keeps the window names in a linked list. It
includes updates to the man page and ChangeLog. The patch is against the
current CVS code. What exactly it does is best described by the modified
portion of the man page:
In addition, the conditions may include one or more window names to
match to. The window names may include the wildcards '*' and '?'. The
window name, icon name, class, and resource are considered when
attempting to find a match. If more than one window name is given, the
implicit operator is a boolean OR -- that is, the condition will be
satisfied if the window has any of those names. Each window name can
begin with '!' which prevents command if any of the window name, icon
name, class or resource match. Mixtures of window names beginning with
'!' and window names without '!' are allowed. The general rule is as
follows: if any of the window names with '!' match, the condition is
not satisfied; otherwise if any of the names without '!' match, or if
there are no names without '!', then the condition is satisfied.
Examples:
Next (Netscape konqueror Mozilla*) WarpToWindow 99 90
This goes to the next web browser window, no matter which of the three
named web browsers is being used.
Next (XTerm !xterm3) WarpToWindow 99 90
This goes to the next xterm window, except that the one named "xterm3"
(with the -name option to xterm) is excluded.
Next (!XTerm !rxvt !emacs !Netscape !konqueror !Mozilla* \
!xdvi !xpdf) WarpToWindow 99 90
This goes to the next window which doesn't have one of the above names.
I'm not subscribed to the fvwm-workers mailing list, so please forward
any comments to me as well as to the list (or yell at me to subscribe for
a while, if that would be appropriate).
Index: ChangeLog
===
RCS file: /home/cvs/fvwm/fvwm/ChangeLog,v
retrieving revision 1.2496
diff -u -u -r1.2496 ChangeLog
--- ChangeLog 31 May 2004 20:19:23 - 1.2496
+++ ChangeLog 1 Jun 2004 01:44:44 -
@@ -1,3 +1,10 @@
+2004-05-31 Norman Yarvin <[EMAIL PROTECTED]>
+
+ * fvwm/fvwm.1.in
+ * fvmw/fvwm.h
+ * fvwm/conditional.c: modified the code for conditions so that
+ multiple window names may be specified in each condition
+
2004-05-31 Dan Espen <[EMAIL PROTECTED]>
* fvwm/fvwm.1.in (COLORSETS): Moved FvwmTheme description of colorsets
Index: fvwm/conditional.c
===
RCS file: /home/cvs/fvwm/fvwm/fvwm/conditional.c,v
retrieving revision 1.93
diff -u -u -r1.93 conditional.c
--- fvwm/conditional.c 9 May 2004 12:59:55 - 1.93
+++ fvwm/conditional.c 1 Jun 2004 01:44:46 -
@@ -382,13 +382,14 @@
*/
void FreeConditionMask(WindowConditionMask *mask)
{
- if (mask->my_flags.needs_name)
- {
- free(mask->name);
- }
- else if (mask->my_flags.needs_not_name)
- {
- free(mask->name - 1);
+ struct namelist *p,*p2;
+
+ for (p=mask->namelist; p;)
+ {
+ free(p->name);
+ p2=p->next;
+ free(p);
+ p=p2;
}
return;
@@ -614,21 +615,16 @@
}
mask->my_flags.needs_same_layer = on;
}
- else if (!mask->my_flags.needs_name &&
-!mask->my_flags.needs_not_name)
- {
- /* only 1st name to avoid mem leak */
- mask->name = condition;
- condition = NULL;
- if (on == 0)
- {
- mask->my_flags.needs_not_name = 1;
- mask->name++;
- }
- else
- {
- mask->my_flags.needs_name = 1;
- }
+ else
+ {
+ struct namelist *p;
+
+ p = (struct namelist *)
+ safemalloc(sizeof(struct namelist));
+ p->name = condition;
+ p->next = mask->namelist;
+ mask->namelist = p;
+ condition = NULL;
}
if (prev_condition)
@@ -663,6 +659,9 @@
int is_on_page;
int is_on_global_page;
FvwmWindow *sf = get_focus_window();
+
Notification: incoming/1292
FVWM Bug Tracking notification new message incoming/1292 Message summary for PR#1292 From: [EMAIL PROTECTED] Subject: Broken _NET_WM_DESKTOP Date: Mon, 31 May 2004 17:22:21 -0500 0 replies 0 followups > ORIGINAL MESSAGE FOLLOWS < >From [EMAIL PROTECTED] Mon May 31 17:22:23 2004 Received: from lserv00.math.uh.edu ([129.7.128.99]) by util2.math.uh.edu with esmtp (Exim 4.30) id 1BUvAk-0006rN-R4 for [EMAIL PROTECTED]; Mon, 31 May 2004 17:22:22 -0500 Received: from localhost (lserv00.math.uh.edu [127.0.0.1]) by lserv00.math.uh.edu (8.11.6/8.11.1) with ESMTP id i4VMMLJ20641 for <[EMAIL PROTECTED]>; Mon, 31 May 2004 17:22:21 -0500 Date: Mon, 31 May 2004 17:22:21 -0500 Message-Id: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Broken _NET_WM_DESKTOP Full_Name: Thomas Nilsson Version: 2.5.10 CVS_Date: 2004-06-01 OS: Linux 2.6.6 X_Server: XFree 4.3.0.1 Submission from: (NULL) (217.73.103.37) In EWMH_SetWMDesktop, you're setting _NET_WM_DESKTOP to 0xFFFE if the window is supposed to be 'sticky across all desktops'. However http://freedesktop.org/Standards/wm-spec/index.html#id2768578 says this value should be set to 0x, so applications which follows this spec will break. We've plugged the bug on our side (xmms) but should be fixed in FVWM aswell. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Notification: incoming/1291
On 30 May 2004 07:15:58 -0500, [EMAIL PROTECTED] wrote: > > Message summary for PR#1291 > From: [EMAIL PROTECTED] > Subject: Pixmaps for borderstyles in 2.5 > > Full_Name: Evgeny Stambulchik > Version: 2.5.8 > CVS_Date: > OS: Linux 2.6.5-gentoo-r1 x86_64 > X_Server: X.Org version: 6.7.0 > Submission from: (NULL) (132.77.4.129) > > > In 2.5.*, when a pixmap is used for window borders, the right border is > rendered separately (with shifted origin) using the pixmap, whereas in > 2.4.* the same pixmap was used, so for gradiented pixmaps it looks now > (2.5) ugly. Please see > http://plasma-gate.weizmann.ac.il/~fnevgeny/tmp/2.4.18.png and > http://plasma-gate.weizmann.ac.il/~fnevgeny/tmp/2.5.8.png. This is a feature. Now the window resizing and moving over other windows do not flicker at all (smooth and fast decorations). I don't think it is possible to have both the old look and not the constant border redrawing on interactive Resize. Yes, it is sad, but flickering is more annoying, I don't even want to recall how ugly it was. So although I would definitelly like to have the way to define border images nicely in the future, I think this may be done after 2.6.x. Regards, Mikhael. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Remove FvwmTheme?
On 31 May 2004 16:41:40 -0400, Dan Espen wrote: > > FVWM CVS writes: > > * fvwm/fvwm.1.in (COLORSETS): Moved FvwmTheme description of colorsets > > into fvwm man page. > > Any reason why the FvwmTheme module should not be completely > removed? Compatibility only. Many configs probably still use the original colorset syntax, i.e. "*FvwmTheme: Colorset". And 2.4.x is forward compatible too, it supports the new Colorset syntax (by: SendToModule FvwmTheme). Maintaining FvwmTheme is a no work. We may remove it in 2.7.x. Regards, Mikhael. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Remove FvwmTheme?
FVWM CVS writes: > * fvwm/fvwm.1.in (COLORSETS): Moved FvwmTheme description of colorsets > into fvwm man page. Any reason why the FvwmTheme module should not be completely removed? -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS dane: 2004-05-31 Dan Espen
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane04/05/31 15:19:23 Modified files: . : ChangeLog docs : ChangeLog todo-2.6 fvwm : fvwm.1.in Log message: 2004-05-31 Dan Espen <[EMAIL PROTECTED]> * fvwm/fvwm.1.in (COLORSETS): Moved FvwmTheme description of colorsets into fvwm man page. 2004-05-31 Dan Espen <[EMAIL PROTECTED]> * todo-2.6: Finished item E.4. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Notification: incoming/1291
FVWM Bug Tracking notification new message incoming/1291 Message summary for PR#1291 From: [EMAIL PROTECTED] Subject: Pixmaps for borderstyles in 2.5 Date: Sun, 30 May 2004 07:13:42 -0500 0 replies 0 followups > ORIGINAL MESSAGE FOLLOWS < >From [EMAIL PROTECTED] Sun May 30 07:13:43 2004 Received: from lserv00.math.uh.edu ([129.7.128.99]) by util2.math.uh.edu with esmtp (Exim 4.30) id 1BUPCA-0001hj-WE for [EMAIL PROTECTED]; Sun, 30 May 2004 07:13:43 -0500 Received: from localhost (lserv00.math.uh.edu [127.0.0.1]) by lserv00.math.uh.edu (8.11.6/8.11.1) with ESMTP id i4UCDgJ04031 for <[EMAIL PROTECTED]>; Sun, 30 May 2004 07:13:42 -0500 Date: Sun, 30 May 2004 07:13:42 -0500 Message-Id: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Pixmaps for borderstyles in 2.5 Full_Name: Evgeny Stambulchik Version: 2.5.8 CVS_Date: OS: Linux 2.6.5-gentoo-r1 x86_64 X_Server: X.Org version: 6.7.0 Submission from: (NULL) (132.77.4.129) In 2.5.*, when a pixmap is used for window borders, the right border is rendered separately (with shifted origin) using the pixmap, whereas in 2.4.* the same pixmap was used, so for gradiented pixmaps it looks now (2.5) ugly. Please see http://plasma-gate.weizmann.ac.il/~fnevgeny/tmp/2.4.18.png and http://plasma-gate.weizmann.ac.il/~fnevgeny/tmp/2.5.8.png. Regards, Evgeny -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
[Mensagem Automatica] Obrigado pelo contato..!!
Mensagem [is that criminal?] recebida. Resposta Automática Recebemos o seu email, em breve será respondido. Conheça o SóGrátizFórum, muitas novidades para você. Acesse o SÓGRÁTIS e o SÓGRÁTIZFÓRUM pelo endereço: http://www.sogratiz.org ou http://www.sogratiz.net E, por favor, vá em ''DÚVIDAS'' la no site, Que tem várias dicas sobre extensões de arquivos e outras coisas, E NO FÓRUM TAMBÉM pode lhe ajudar. SóGrátiz - Sempre uma novidades para você...!! Jogos On-line..??? www.sogratis.com -- é divertimento garantido!! Obrigado. Equipe SóGrátiz. -- Visit the official FVWM web page at http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
