Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bellcore!jello!aw
From: aw@jello.bae.bellcore.com (Andrew Wason)
Newsgroups: comp.windows.x
Subject: Re: twm name matching too lax
Message-ID: <1991Apr12.232713.7588@bellcore.bellcore.com>
Date: 12 Apr 91 23:27:13 GMT
References: <11992@dog.ee.lbl.gov> <9104111831.AA07464@excess.lcs.mit.edu>
Sender: usenet@bellcore.bellcore.com (Poster of News)
Reply-To: aw@bae.bellcore.com
Organization: Bell Communications Research
Lines: 30

In article <9104111831.AA07464@excess.lcs.mit.edu>, converse@expo.lcs.mit.EDU writes:
>> bar.  The problem is that twm only requires that the first n characters of
>> the client/class in the list match the name of the client/class one wishes
>
>Right.  We've received bug reports on this.  The string prefix matching 
>is a bug, not a feature.


I thought this was a feature.  The twm man page seems to imply that it is
(at least it doesn't say it is a bug):

     [...]
     When a variable containing a list  of  strings  representing
     windows  is  searched  (e.g.  to determine whether or not to
     enable autoraise as shown above), a string is considered  to
     match  a  window  if  it  is a case-sensitive prefix for the
     window's name name (given by the WM_NAME  window  property),
     resource name or class name (both given by the WM_CLASS win-
     dow property).
     [...]
     Lists of Window name prefix strings are indicated by win-list.


Andrew

_______________________________________________________________________________

Andrew Wason                                       Bell Communications Research
aw@bae.bellcore.com                                Piscataway, NJ
bellcore!bae!aw