I asked this in the Wary thread, but it mustn't be sufficiently technical to prompt anyone to answer.
![Confused :?](./images/smilies/icon_confused.gif)
Wary doesn't have a MENU entry for the screensaver. I think older puppies did.
But thats not screensaver you need to key in your password instead of just moving your mouse.xlock -mode blank
Screensaver in Wary:Shep wrote:Can the screensaver be activated by a keypress to blank the screen immediately?
I asked this in the Wary thread, but it mustn't be sufficiently technical to prompt anyone to answer.![]()
Wary doesn't have a MENU entry for the screensaver. I think older puppies did.
Code: Select all
<Key mask="A" key="Esc">xlock `cat /root/.config/Xlock/xlockscreenparams`</Key>
That file doesn't exist, at the moment. Your Xlock suggestion might be ideal, because I would use its option to not mess with passwords:Dougal wrote:You probably want to create a JWM keybinding to run the xlock command.
For example, Alt+Esc (this goes in ~/.jwm/jwmrc-personal):Code: Select all
<Key mask="A" key="Esc">xlock `cat /root/.config/Xlock/xlockscreenparams`</Key>
Code: Select all
+/-nolock
The nolock option causes xlock to only draw the patterns and not lock the display. A key press or a mouse click will terminate the screen saver.
That's strange... if JWM is used that file should exist since it's what the configuration utility changes (and has some default settings).Shep wrote:That file doesn't exist, at the moment.Dougal wrote:You probably want to create a JWM keybinding to run the xlock command.
For example, Alt+Esc (this goes in ~/.jwm/jwmrc-personal):Code: Select all
<Key mask="A" key="Esc">xlock `cat /root/.config/Xlock/xlockscreenparams`</Key>
Code: Select all
<Include>/root/.jwm/jwmrc-personal</Include>
There is no /root/.jwmrcDougal wrote:That's strange... if JWM is used that file should exist since it's what the configuration utility changes (and has some default settings).
You should look in ~/.jwmrc for Include lines like:Code: Select all
<Include>/root/.jwm/jwmrc-personal</Include>
Code: Select all
# find / -name 'xlockscreenparams'
#
Code: Select all
display all 1493 possibilities? (y or n)
Well, the "personal" files are what I mentioned in the first place: that's where you add the new keybinding.Shep wrote:There is no /root/.jwmrcDougal wrote:That's strange... if JWM is used that file should exist since it's what the configuration utility changes (and has some default settings).
You should look in ~/.jwmrc for Include lines like:Code: Select all
<Include>/root/.jwm/jwmrc-personal</Include>
The only files in /root/.jwm are jwm_colors jwmrc-personal jwmrc-personal2 jwmrc-theme themes
There are no hidden files. The two personal files seem identical.
The xlockscreenparams file is created when you configure xlock... I just looked at Barry's xlock_gui package and it still seems to use it.When I put your alt esc idea into one of the personal files, it doesn't fire off xlock. When in a console the ALT-ESC combo produces:Code: Select all
# find / -name 'xlockscreenparams' #
Code: Select all
display all 1493 possibilities? (y or n)
Code: Select all
<!-- IMPORTANT, ONLY EDIT /etc/xdg/templates/_root_.jwmrc -->
<!-- jwm menu for puppy Linux -->
Code: Select all
<Key mask="A" key="Tab">next</Key>
<Key mask="A" key="F4">close</Key>
<Key mask="A" key="#">desktop#</Key>
<Key mask="A" key="F1">root:3</Key>
<Key mask="A" key="F2">window</Key>
Code: Select all
<Key mask="A" key="F3">close</Key>
Code: Select all
<Include>/root/.jwm/jwmrc-theme</Include>
<Include>/root/.jwm/jwmrc-personal</Include>
That's just the template used for generating ~/.jwmrc -- you need to run fixmenus to regenerate it...Shep wrote:Now, this is looking promising: in file etc/xdg/templates/_root_.jwmrc we read:I edited it by adding a new entry, and restarted JWM but the new entry had no effect.Code: Select all
<!-- IMPORTANT, ONLY EDIT /etc/xdg/templates/_root_.jwmrc --> <!-- jwm menu for puppy Linux -->
That doesn't seem to make sense... unless you regenerate the menu it should not have any effect and even if you do, I can't see why it will behave that way unless:What's weird is that if I change an already defined key combination, then that works, but if I add a new entry, it doesn't work.
For example, here are some already defined entries:If I alter this so that alt-F4 now performs "next" then that works and it does perform the next function. But if I add a 6 th entry to this block, viz.Code: Select all
<Key mask="A" key="Tab">next</Key> <Key mask="A" key="F4">close</Key> <Key mask="A" key="#">desktop#</Key> <Key mask="A" key="F1">root:3</Key> <Key mask="A" key="F2">window</Key>
then alt-F3 is not recognised as a defined combination.Code: Select all
<Key mask="A" key="F3">close</Key>
Code: Select all
# find / -name '.jwmrc'
/root/.jwmrc
Code: Select all
# find / -name 'xlockscreenparams'
/root/.config/Xlock/xlockscreenparams