Ok, I understand now it is valid Windows syntax, but when I run the
batch files they look for brltty.conf in //etc/brltty.conf.
I was trying to figure out why that is: First I ran 'brlttycnf.exe'.
Then 'run-brltty.bat'.
I get this log
2022-10-24@20:50:48.125 BRLTTY 6.5 rev BRLTTY-6.5+ [https://brltty.app/]
2022-10-24@20:50:48.145 Log Level: info
2022-10-24@20:50:48.145 Messages Locale: en_US
2022-10-24@20:50:48.145 Messages Domain: brltty
2022-10-24@20:50:48.145 Messages Directory:
C:/user/brltty-win-6.5-0-libusb-1.0/brltty-win-6.5-0-libusb-1.0/bin/../share/locale
2022-10-24@20:50:48.145 Working Directory:
C:\user\brltty-win-6.5-0-libusb-1.0\brltty-win-6.5-0-libusb-1.0
2022-10-24@20:50:48.145 Configuration File: //etc/brltty.conf
2022-10-24@20:50:48.145 Preferences File: brltty.prefs
On 10/24/2022 4:05 PM, Dave Mielke wrote:
[quoted lines by Chevelle on 2022/10/24 at 15:26 -0400]
It is interesting that the batch files in the Windows release contain this
line.
set programFolder=%~dp0
It doesn't seem to be valid Windows syntax. It doesn't appear to work on my
system.
Yes, it's valid. It means the directory component of the path to the script.
Maybe what is intended is to get the current install directory.
Perhaps it could say:
set programFolder=%CD%
'CD' would be the current directory.
No, that wouldn't be acceptabe. For example, it wouldn't work right if your
current directory was somewhere else and you were invoking the script via its
absolute path.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty
