On Wed, Feb 02, 2011 at 09:13:44AM -0800, Joe Riel wrote: > I didn't get InitialMapCommand to do anything. Echo is supposed to > print to stderr, but I don't see the message when launching the > application from the command line.
Well, that would typically be in ~/.xsession-errors if X redirects there. Or somewhere else if you've explicitly sent STDERR from FVWM somewhere else (doubtful). But really, just because there might have been a typo on a given line, or you wanted to see if something had worked, the suggestion of using InitialMapCommand from me was a bit of a red herring, because the options to the style command are tokenised and run or skipped depending if something's wrong. Hence it's perfectly possible for you to do this: Style foo opfdkjfd, fdjkjlk, Sticky, l, InitialMapCommand Beep And still hear a beep for window "foo", regardless of the obvious errors on that line. That then doesn't guarantee that "opfdkjfd" worked, or was supposed to. But note that the question was meaningless anyway; you would have gotten an error to STDERR (heh -- see above as to where that might get logged). No news from FVWM is typically good news for things like style parsing -- beyond that, there's other ways of tracking down problems where you think things should be working but aren't. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
