Replies: 5 comments
-
What happens when you try:
or:
|
Beta Was this translation helpful? Give feedback.
-
Nothing happens, but I am probably missing some step here. IceWM is started by the display manager, and I can't see any console output from it. If it is logged somewhere, then I don't know where to look for it. However, when I try: |
Beta Was this translation helpful? Give feedback.
-
gives you the file where icewm output is logged. That enables you to discover by experimenting what is the matter. I want you to become self-sufficient, because I don't wish to answer loads of questions by every new user, as you may understand, hopefully. |
Beta Was this translation helpful? Give feedback.
-
Both your help and your approach are appreciated. I prefer to understand things I use. So, using That means IceWM directly executes echo command, with rest as arguments, not passing it through bash, which would process the || chaining. So, the solution is: So far it seems to work as expected. Thanks. |
Beta Was this translation helpful? Give feedback.
-
I'll give you a more icewm-ish style solution as a reward for your hard work:
Depending on your configuration and goals this may also work:
|
Beta Was this translation helpful? Give feedback.
-
Due to some weird bug with FluxBox (messing up behavior of some GUI apps a bit), I'm now trying out IceWM.
In FluxBox, I have defined a keyboard shortcut that either focuses an application if it is started already, or starts it otherwise. When I tried to do the same in IceWM, it doesn't seem to work:
~/.icewm/keys:
This correctly switches to Firefox if it is already started, but otherwise it doesn't start Firefox. It seems like the || isn't processed in usual shell-like manner in IceWM.
Any idea how to do this simply?
Beta Was this translation helpful? Give feedback.
All reactions