JWM vs Rox filer keybind in FossaPup (Solved)

[miltonx]

I am using fossapup64-9.5. I noticed that the JWM keybind setting does not work. I tried JWM settings, also tried editing /root/.jwmrc. No effect.
Then I used rox filer to set keybind, ie, dragging an application to desktop then editing the shortcut icon to add keybind. This works.
Looks like rox filer overrides JWM's keybind settings. But the pain is that you have to drag an icon to desk in order to set keybind.
Any way to 1) let Jwm take control, or 2) let rox filer set keybind without dragging app to desktop?

[williams2]

You can edit the hidden file /root/.xinitrc
change the line near the bottom of the file from this:

Code: Select all

which $CURRENTWM && exec $CURRENTWM

to these 2 lines:

Code: Select all

( rox -p= ; sleep 2 ; rox -p rox -p /root/Choices/ROX-Filer/PuppyPin ) & disown
which $CURRENTWM && exec $CURRENTWM

This turns rox off, allows JWM to get the key bindings, then starts the rox desktop again.
It might be better to sleep 5 seconds rather than sleep 2

[MochiMoppel]

Any way to 1) let Jwm take control, or

jwm has control. At least that's how it is supposed to work. If both jwm and ROX-Filer share the same key combination for a shortcut, jwm will have precedence. Test it in FossaPup: Does F12 trigger the jwm menu? If so assign F12 to a desktop icon and see if F12 triggers the desktop shortcut. Should still trigger the menu.

2) let rox filer set keybind without dragging app to desktop?

You can assign it to a panel item, if you use a panel, but technically it's the same as using a desktop item,
Other than that there is no way

This turns rox off, allows JWM to get the key bindings, then starts the rox desktop again.

Are you sure? It doesn't turn ROX-Filer off, it just removes PuppyPin and adds it again while ROX-Filer keeps running. I see no point in doing this.

[miltonx]

Does F12 trigger the jwm menu? If so assign F12 to a desktop icon and see if F12 triggers the desktop shortcut. Should still trigger the menu.

F12 seems to be a different thing, kind of hard coded in jwm, whereas keybinds are at the user configurable level, at which jwm yields to Rox. After I use JWM desk manager to set keybinds, the setting does appear in /root/.jwm/jwmrc-personal, but it simply does not work.

[MochiMoppel]

This doesn't answer my question.

[miltonx]

This doesn't answer my question.

Yes it still trigers the jwm menu.

[miltonx]

You can edit the hidden file /root/.xinitrc
change the line near the bottom of the file from this:

Code: Select all

which $CURRENTWM && exec $CURRENTWM

to these 2 lines:

Code: Select all

( rox -p= ; sleep 2 ; rox -p rox -p /root/Choices/ROX-Filer/PuppyPin ) & disown
which $CURRENTWM && exec $CURRENTWM

This turns rox off, allows JWM to get the key bindings, then starts the rox desktop again.
It might be better to sleep 5 seconds rather than sleep 2

Did it. X fails to start.

[MochiMoppel]

Yes it still trigers the jwm menu.

So this shows that your assumption ("Looks like rox filer overrides JWM's keybind settings') was wrong. ROX-Filer does not override JWM.

If your JWM settings don't work they either contain bad instructions or you forgot to run the command jwm -restart after making the changes.

[rockedge]

Code: Select all

jwm -reload
jwm -restart

[williams2]

Are you sure? It doesn't turn ROX-Filer off, it just removes PuppyPin and adds it again while ROX-Filer keeps running

Usually, when X starts, rox is running a single instance, and no rox file windows are opened.
I usually have no panels, and I think FossaPup by default doesn't open any rox panels.

If those assumptions are correct, then rox -p= should close the rox pinboard, which will cause the rox executable to exit.

"killall ROX-filer" would do about the same thing, but it would work even if there are panels open, or other instances of rox, or if there are any rox windows showing files.

Did it. X fails to start.

I did not test it, and I was running BionicPup at the time anyway.
I just tested it in FossaPup, and X starts, on my machine.

As far as I know, if there is a conflict of 2 or more processes binding to a shortcut, what ever starts running first will bind to the key shortcut and other processes will fail to bind the shortcut.

I had a problem where I wanted the console icon on the rox pinboard/desktop to bind to Winkey+T but jwm (or something) had already grabbed the Win+T shortcut. Rox would print an error message, but rox (or something) would change the PuppyPin file and remove the shortcut from the file. I worked around the problem by keeping a copy of the pinboard the way I want it, and copying it back to rox's PuppyPin file every time X starts. FossaPup is doing something like that that anyway,

[MochiMoppel]

If those assumptions are correct, then rox -p= should close the rox pinboard,

It does

which will cause the rox executable to exit.

It does not - or more precisely: rox wasn't running in the first place. In all distros I know rox is a very simple wrapper script that closes as soon as it has passed the received arguments to another wrapper script (/usr/local/apps/ROX-Filer/AppRun) which finally calls the main ROX-Filer executable. There is always only one ROX-Filer instance running. It may create windows and the pinboard (which is just another but special window), but all windows belong to the same process ID of ROX-Filer. That's the way I know it but maybe your system is different.

[williams2]

I don't wish to confuse the OP, but:

There is always only one ROX-Filer instance running

Assuming the pinboard is there, you can add 2 more rox instances like this:

Code: Select all

rox -n /bin

and

Code: Select all

rox -n /root

Code: Select all

ps|grep [R]OX
 4960 root      0:01 /usr/local/apps/ROX-Filer/ROX-Filer -p /root/Choices/ROX-Filer/PuppyPin
 5556 root      0:00 /usr/local/apps/ROX-Filer/ROX-Filer -n /bin
 5599 root      0:01 /usr/local/apps/ROX-Filer/ROX-Filer -n /root

Usually, normally, typicially, there is one instance of rox running at any time.

Yes, the name of the rox filer executable is ROX-Filer, and as I said before, given certain assumptions,
"killall ROX-Filer" will do about the same thing as "rox -p="

"rox" is easier to type than "roxfiler". Personally, I often open files and dirs with rox, so I have a script named "r" that does the same thing as "rox". A warning, some versions of Linux have a program named "r" already installed that will erase a file if you open it like this:

Code: Select all

r readme.txt

Again, I have no wish to confuse the OP by addressing these comments.

[miltonx]

I did not test it, and I was running BionicPup at the time anyway.
I just tested it in FossaPup, and X starts, on my machine.

Sorry, it was a typo yesterday. Now it works. I can set keybinds by editing .jwmrc now. Funny things is that the jwm desk manager hotkey config gui is still ineffective.

[miltonx]

If your JWM settings don't work they either contain bad instructions or you forgot to run the command jwm -restart after making the changes.

Tested on pristine fossapup64, no aapps installed, no settings done. Restarted jwm after setting hotkey. Still doesn't work.

[rockedge]

Funny things is that the jwm desk manager hotkey config gui is still ineffective.

I wonder if the configuration GUI is writing to the wrong .jwmrc file.

[bigpup]

If your JWM settings don't work they either contain bad instructions or you forgot to run the command jwm -restart after making the changes.

Tested on pristine fossapup64, no aapps installed, no settings done. Restarted jwm after setting hotkey. Still doesn't work.

Set it by doing exactly what?
What exact changes did you make?
Give us one you did so we can try it.

If you have an active program window open, that has it's own hotkeys. Those will usually override and those same hotkeys only work in the program.
Except jwm very specific ones.

[MochiMoppel]

If you have an active program window open, that has it's own hotkeys. Those will usually override and those same hotkeys only work in the program.

Unfortunately not.
Example: Open the "View" menu of mtPaint. As you see the F12 key is supposed to show the dock. Does it?

[miltonx]

If your JWM settings don't work they either contain bad instructions or you forgot to run the command jwm -restart after making the changes.

Tested on pristine fossapup64, no aapps installed, no settings done. Restarted jwm after setting hotkey. Still doesn't work.

Sorry for the sloppy test and description.
Did it again:
1) Set JWM desk manager hotkey setting, tried restarting jwm & rebooting. Never worked.
2) Edited /root/.jwmrc. Both restarting jwm and rebooting worked. I forgot to test this yesterday.

Truly, jwm's rc hotkey setting is not overridden. (However, i have not tried a same keybind between jwm and rox to test clash situation) It is the graphical tool that is ineffective. I should have been more thorough with my testing.

[MochiMoppel]

Did it again:
1) Set JWM desk manager hotkey setting, tried restarting jwm & rebooting. Never worked.

You should tell us exactly what setting you tried.
I tried JWMdesk and it worked. After your setting you should receive the message "Shortcut has been successfully added". Did you? JWMdesk writes to /root/.jwm/jwmrc-personal, not /root/.jwmrc (a file you should not edit manually)
There is no need for you to restart jwm or reboot, JWMdesk takes care of that.
So after you made your "did not work" changes you should check the file /root/.jwm/jwmrc-personal and see if the file has been updated as expected.

[miltonx]

- Started fossapup64, ram only, no save;
- JWM desk manager -> hotkey manager -> set Mod4 + z to action: geany.
- Clicked ok, showed successfully added shortcut.
- Pressed super-z, nothing.
- Rebooted with saving, pressed super-z, nothing.
- Checked /root/.jwm/jwmrc-personal, seeing <Key mask="4" key="z">geany</Key>

Note: Previous testing showed mod4-z works by editing /root/.jwmrc. I deleted that pupsave, booted to ram to make sure there is no overlap.

[MochiMoppel]

- JWM desk manager -> hotkey manager -> set Mod4 + z to action: geany.

Must be exec:geany

/root/.jwm/jwmrc-personal will then read
<Key mask="4" key="z">exec:geany</Key>

[miltonx]

- JWM desk manager -> hotkey manager -> set Mod4 + z to action: geany.

Must be exec:geany

/root/.jwm/jwmrc-personal will then read
<Key mask="4" key="z">exec:geany</Key>

OMG, I edited the config file several times only to neglect that! Sorry for leading you through such a silly chase.

[bigpup]

If you have an active program window open, that has it's own hotkeys. Those will usually override and those same hotkeys only work in the program.

Unfortunately not.
Example: Open the "View" menu of mtPaint. As you see the F12 key is supposed to show the dock. Does it?

Now you know what usually is saying.

I deleted the F12 entry in JWM Hotkey.
F12 now works in Mtpaint.

Really it is best to try not to use hotkeys in JWM that are also used in specific programs.

Not sure where those preset entries in JWM Hotkeys come from.
I consider them examples to use, maybe.
You can delete, add, or change any of them.