Volker Reichelt <reichelt_at_igpm.rwth-aachen.de> writes:
> On 21 Mar, Dan Espen wrote:
> > fvwm-bug_at_fvwm.org writes:
> >> FVWM Bug Tracking notification
> >>
> >> new message incoming/1003
> >>
> >> From: reichelt_at_igpm.rwth-aachen.de
> >> To: fvwm-bug_at_fvwm.org
> >> Subject: nedit windows get properties from other programs
> >> Date: Fri, 21 Mar 2003 07:49:58 -0600
> >>
> >> I have the following line in my .fvwmrc2 file:
> >> Style XClock Sticky
> >> to make xclock sticky.
> >>
> >> If I open an nedit window for a file named "XClock" by issuing the command
> >> "nedit XClock" the nedit window gets sticky, too.
> >>
> >> I'm not sure whether this is a bug in fvwm or in nedit (version 5.3RC1)
> >> or even a feature.
> >
> > Its a limitation of the way styles work.
> > They match on a windows name, class, or resource.
>
> Ok.
>
> > You can start xclock like this:
> >
> > xclock -name MakeMeSticky
> >
> > and then change the style like this:
> >
> > Style MakeMeSticky Sticky
>
> That just shifts the problem.
> It would be nice if I could tell the style just to match class and
> resource since I have:
>
> Name: XClock - /home/foo/bar
> Icon Name: XClock
> Class: NEdit
> Resource: nedit
>
> Is that possible? If not, is there a chance that something like this
> could be implemented?
Its on the todo list. Maybe some day.
--
Dan Espen E-mail: dane_at_mk.telcordia.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Mar 21 2003 - 10:47:10 GMT