Re: [cvs.lp.se #14] [PATCH] Multi-entry lists, configuration check mode

2003-02-21 Thread Thomas Linden
On Fri, Feb 21, 2003 at 09:00:13AM +0100, Richard Levitte - VMS Whacker wrote:
 In message [EMAIL PROTECTED] on Fri, 21 Feb 2003 
08:46:31 +0100, Claude Lecommandeur [EMAIL PROTECTED] said:
 
 claude.lecommandeurWouldn't the best solution to have support for
 claude.lecommandeur decent (perlish) regular expressions :
 claude.lecommandeur 
 claude.lecommandeur  ^(foo|bar)$   value
 claude.lecommandeur 
 claude.lecommandeurregex can do this.
 
 Hmm, in certain cases, that would mean using part of the GNU C
 Library, which is licensed under the LGPL.  What would that mean for
 me, distribution-wise?

if ctwm is compiled on linux, the GNU Clibrary is used anyway, so this
shouldn't hurt you.

You could also use the PCRE library, which is compatible to perl
regular expressions...


Tom


-- 
 [ Thomas Linden - http://www.daemon.de/ - [EMAIL PROTECTED] ] 
 $_=`perl -v`;s;^.*ll;;s;$^=unpacku,'8V]D;')E```;s;\W;;gs;$/=7*
 ($^=~s;.;;g);%^=map{$_=1}split//,lc;$_=join$\,(sort keys(%^))[map{
 ord($_)-$/}split//,'1I7E13?@E:7C1A7C=1:357C'];s0(.) \U$1g;print;



Re: [cvs.lp.se #14] [PATCH] Multi-entry lists, configuration check mode

2003-02-21 Thread Matthew D. Fuller
On Fri, Feb 21, 2003 at 09:00:13AM +0100 I heard the voice of
Richard Levitte - VMS Whacker, and lo! it spake thus:
 In message [EMAIL PROTECTED] on Fri, 21 Feb 2003 
08:46:31 +0100, Claude Lecommandeur [EMAIL PROTECTED] said:
 
 claude.lecommandeurWouldn't the best solution to have support for
 claude.lecommandeur decent (perlish) regular expressions :
 claude.lecommandeur 
 claude.lecommandeur  ^(foo|bar)$   value
 claude.lecommandeur 
 claude.lecommandeurregex can do this.
 
 Hmm, in certain cases, that would mean using part of the GNU C
 Library, which is licensed under the LGPL.  What would that mean for
 me, distribution-wise?

I don't think it matters; you're _already_ using part of the GNU C
Library in certain cases (i.e., on any system with glibc :).  The
regex(3) functions from Henry Spencer aren't [L]GPL'd, and there's also
the choice of PCRE; either, as far as I can tell, are mostly BSD-style
licensed.

I actually did momentarily consider using regular expressions when I
wrote the original patch, but I dismissed it as absurd overkill (and for
_ME_ to pass up on overkill is unusual ;) and just went for
comma-seperated.

Now, one idea is to go to |-seperated lists inside ()'s; sort of
hand-implementing just the (a|b|c) part of regular expressions.  Thus,
the code would treat foo as it does now, but special-case if the entry
started with a '(' as a |-seperated list.  That would work; would take
about 5 minutes to update the code for, would make it perhaps more
obvious what it's doing...  And anybody who makes a window class whose
name starts with '(' deserves what they get   ;-p


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet



Re: [cvs.lp.se #14] [PATCH] Multi-entry lists, configuration check mode

2003-02-21 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Fri, 21 Feb 2003 10:32:50 
-0600, Matthew D. Fuller [EMAIL PROTECTED] said:

fullermd On Fri, Feb 21, 2003 at 09:00:13AM +0100 I heard the voice of
fullermd Richard Levitte - VMS Whacker, and lo! it spake thus:
fullermd  In message [EMAIL PROTECTED] on Fri, 
21 Feb 2003 08:46:31 +0100, Claude Lecommandeur [EMAIL PROTECTED] said:
fullermd  
fullermd  claude.lecommandeurWouldn't the best solution to have support for
fullermd  claude.lecommandeur decent (perlish) regular expressions :
fullermd  claude.lecommandeur 
fullermd  claude.lecommandeur  ^(foo|bar)$   value
fullermd  claude.lecommandeur 
fullermd  claude.lecommandeurregex can do this.
[...]
fullermd Now, one idea is to go to |-seperated lists inside ()'s;
fullermd sort of hand-implementing just the (a|b|c) part of regular
fullermd expressions.  Thus, the code would treat foo as it does
fullermd now, but special-case if the entry started with a '(' as a
fullermd |-seperated list.  That would work; would take about 5
fullermd minutes to update the code for, would make it perhaps more
fullermd obvious what it's doing...  And anybody who makes a window
fullermd class whose name starts with '(' deserves what they get
fullermd ;-p 

I'm still dubious about this.  The reason is that I see it like a
string is a string is a string and nothing but a string.  From a
user's point of view, I'd find it rather confusing if some strings
didn't behave like strings do elsewhere.  Or to follow up on the
regexp idea, what about this?

  ^(foo|bar)$ \1value

But really, if we're to introduce regexps, they should come with a
different syntax, for example with / as delimiter instead of  (now
we're etting Perly!):

  /^(foo|bar)$/ \1value

-- 
Richard Levitte | http://richard.levitte.org/ | Spannv. 38, I
Levitte Programming | http://www.lp.se/   | S-168 35 Bromma
T: +46-708-26 53 44 | | SWEDEN
 Price, performance, quality...  choose the two you like



Re: [cvs.lp.se #14] [PATCH] Multi-entry lists, configuration check mode

2003-02-21 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Fri, 21 Feb 2003 
18:38:10 +0100, [EMAIL PROTECTED] (Johan Vromans) said:

jvromans Well, in this case it doesn't matter much, since it's not Perl but
jvromans PCRE we're dealing with... OTOH, why not embed Perl in ctwm and use
jvromans real Perl to drive the configuration[1].

*cough* and when do you expect CTWM to read your mail?  :-)

Seriously, I haven't done any embedded Perl stuff, so I'm out on a
very thin limb here, but I get the impression that we risk a bit of
bloat with it.  If I'm wrong, please enlighten me.

-- 
Richard Levitte | http://richard.levitte.org/ | Spannv. 38, I
Levitte Programming | http://www.lp.se/   | S-168 35 Bromma
T: +46-708-26 53 44 | | SWEDEN
 Price, performance, quality...  choose the two you like



Re: Preview: 3.7 alpha1

2003-02-21 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Fri, 21 Feb 2003 
19:28:02 +0100, Johan Vromans [EMAIL PROTECTED] said:

jvromans Richard Levitte - VMS Whacker [EMAIL PROTECTED] writes:
jvromans 
jvromans  9 - Changed Imakefile to support a distribution target.
jvromans 
jvromans This target seems to require a 'tardy' tool. This is not on any of my
jvromans systems. What is it supposed to do?

It's a tar archive editor, where the metadata, including aspects of
the file path, can be changed.  I'm quite fond of it.  You can find it
as part of most *BSD and Linux distributions, as well as in source at
http://www.canb.auug.org.au/~millerp/tardy.html .

-- 
Richard Levitte | http://richard.levitte.org/ | Spannv. 38, I
Levitte Programming | http://www.lp.se/   | S-168 35 Bromma
T: +46-708-26 53 44 | | SWEDEN
 Price, performance, quality...  choose the two you like



Re: placement in other workspaces?

2003-02-21 Thread Bjorn Knutsson
On 21 Feb 2003 09:46, James Pace wrote:
 
 I've got 9 workspaces, and at startup I want to put some windows
 in WS 1, and mozilla in workspace 2 and other stuff in other
 workspaces.
 
 Can I do that?

Sure, lets say you have the following defined:

WorkSpaces {# Define these workspaces
first {goldenrod black goldenrod black }
mozilla   {light sea green black light sea green black }
other {magenta3 black magenta3 black }
}

Occupy {# Default occupy
Workspace mozilla {
mozilla-bin Mozilla-bin mozilla Mozilla
}
Workspace other {
  xmms
}
}

Now, all your Mozillas will always come up in the mozilla workspace,
and xmms will always open in the other workspace.

You can do the same trick with any other application, just associate
its (X) name with a workspace.

If your application allows you to use -xrm (xterm would be one such
example), you could start them from a shell in the first workspace
with:

# xterm -xrm ctwm.workspace:other 

to have them actually show up in the other workspace.

/Björn



Re: [cvs.lp.se #14] [PATCH] Multi-entry lists, configuration check mode

2003-02-21 Thread Kai Großjohann
Matthew D. Fuller [EMAIL PROTECTED] writes:

 OTOH, comma-seperated lists are a common paradigm (I hate that word,
 sometimes) even in such illogical languages as English.

How about using curly braces for lists?  That's used elsewhere in
.ctwmrc, so it would be easy to understand for the user.
-- 
A preposition is not a good thing to end a sentence with.