Page 1 of 1

Using kchmviewer

Posted: Sun Jan 28, 2024 12:45 am
by AZJIO
I solved the problems of running help using kchmviewer. Previously, kchmviewer opened a new window every time. Now kchmviewer is being forcibly closed.

Commandline: sh
Arguments: /home/user/Apps/purebasic/tools/kill-kchmviewer.sh %WORD /home/user/Apps/purebasic/PureBasic.chm

The contents of the file kill-kchmviewer.sh

Code: Select all

#!/bin/sh
# sh
# /home/user/Apps/purebasic/tools/kill-kchmviewer.sh %WORD /home/user/Apps/purebasic/PureBasic.chm
# wmctrl -F -c 'kchmviewer - Title'
# killall kchmviewer
kchmviewer -token alf -index $1 $2
Previously, I used the commands

Code: Select all

Commandline: kchmviewer
Arguments: -token alf -index %WORD /home/user/Apps/PureBasic/PureBasic.chm

Commandline: kchmviewer
Arguments:-token alf -search %WORD /home/user/Apps/PureBasic/PureBasic.chm

Commandline: xchm
Arguments: /home/user/Apps/PureBasic/PureBasic.chm

Re: Using kchmviewer

Posted: Mon Jan 29, 2024 7:17 pm
by deseven
Shells in non-interactive mode could have a different PATH. Check that kchmviewer is accessible that way. You can add something like

Code: Select all

echo "$PATH" > /tmp/debug.txt
to your script to make sure that PATH actually includes a directory where your kchmviewer is located.

Re: Using kchmviewer

Posted: Sat Feb 01, 2025 4:38 pm
by AZJIO