meshcore-dev/meshcore-cli
1
0
Fork 0
mirror of https://github.com/meshcore-dev/meshcore-cli.git synced 2026-04-20 22:13:48 +00:00
Code Issues Projects Releases Packages Wiki Activity

Merge pull request #52 from jburgess777/patch-1

Browse source 
Fix minor typos and formatting in README.md
This commit is contained in:
fdlamotte 2026-03-09 19:37:36 -04:00 • committed by GitHub
commit 09e333960d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -1,6 +1,6 @@
# meshcore-cli
meshcore-cli : CLI interface to MeschCore companion app over BLE, TCP or Serial
meshcore-cli : CLI interface to MeshCore companion app over BLE, TCP or Serial
## About
@ -44,11 +44,11 @@ If using BLE, don't forget to pair your device first (using `bluetoothctl` for i
Configuration files are stored in `$HOME/.config/meshcore`
If the directory exists, default ble address and history will be stored there.
If the directory exists, default BLE address and history will be stored there.
If there is an initialization script file called `init`, it will be executed just before the commands provided on command line are executed (and after evaluation of the arguments).
Init files can also be defined for a given device, meshcore-cli will look for `<device-name>.init` file in configuration directory (usefull to specify timeout for contacts that are behind bridges with `contact_timeout` command).
Init files can also be defined for a given device, meshcore-cli will look for `<device-name>.init` file in configuration directory (useful to specify timeout for contacts that are behind bridges with `contact_timeout` command).
### Arguments