On Wed, Nov 22, 2017 at 09:52:21PM +0530, Bhupendra Kumar Jain wrote: > Hi, > > A small correction to the last email in bold. > > > *But if I try below command then it doesn't make them back sticky.* > > *FvwmCommand 'Style "xterm" NoSticky'*
So as per usual, you're about as forthcoming as ever in terms of what it is you're trying to achieve. So I'll guess, by giving you as many examples as I can, hoping that I hit on the right one, and this somehow applies to your situation. Here's a tip: for the future, rather than sending out many different emails with specific issues you're having, why not outline your specific problems so that I (and others) have to spend time drip-feeding you this information en masse. Regardless of how FVWM receives your commands (whether it's via FvwmCommand or a config file, or FvwmConsole, etc.), it will behave the same way. In your case, you have a few ways of ensuring a Sticky state: 1. Style Foo Sticky Will make "Foo" Sticky. All "Foo"s will therefore be sticky, and it wouldn't pertain to just one specific window. For that, you've already found out about the "WindowId" command. However in the general case, you probably want to use conditional commands to achieve the same thing, as a window's ID is only valid for the lifetime of the window (and/or the window manager is restarted -- in which case when the window is recaptured, it gets a new ID). Examples of this include: Next (Foo, CurrentPage) WindowStyle Sticky Next (FooBar, CurrentPage) WindowStyle !Sticky 2. Stick command versus Style condition As with point 1., above, you'll note I'm using the Style command to change a window's state. There's nothing wrong in that, however, there is also the "Stick" command which achieves the same thing: Next (MyWindow) Stick This will toggle the state of the window between being sticky or not, depending on the state of the window at that time. Why is there a difference between a style state and a Stick command? History, and poor planning, and no one has yet removed one in favour of the other. Personally speaking, I wouldn't say there's a compelling reason to use either notion. Pick one which makes sense to you. When I was referring to "Pick" before is that this won't assume a window context when executing a command if there isn't one already; making you choose the window you wanted. If you wanted to always be guaranteed a window to select, you would use: NoWindow Pick (Foo) Stick -- Thomas Adam
