The code text uses the glossary words in more places

A final pass over the docstrings and comments: "the own X of Y" is now
"Y's own X" (84 places), a navigation entry is a screen on the stack, our
node is our node, a paint is a paint, the quoted UX labels are in code
font, and a list of punctuation glyphs is in code font.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Opus 5.5 committed 2026-10-06 21:45:04 -04:00
1 parent bc51115d24
commit efc02ddced
51 files changed
+116 -116

No files matched your search

+1 -1
View File
@@ -13,7 +13,7 @@ This script gives that explanation. It is standalone and uses only the standard
the user can paste it onto any machine that runs any version of MeshTerm. It prints one
verdict with the fix.
The script must run under the own interpreter of MeshTerm. This is the important point. A
The script must run under MeshTerm's own interpreter. This is the important point. A
Mac usually has three Pythons, and only one of them is the Python of the app. Only the
certificate store of that Python is the store that the map uses. If another Python starts
the script, the script finds the installed ``meshterm`` command and reads the interpreter
@@ -3,8 +3,8 @@
# calculinux-console-font-6x8.sh -- build and install meshterm8.psf.gz, the 6x8 (53x40)
# console font for the PicoCalc display.
#
# LICENCE -- READ THIS FIRST. The base bitmap that is embedded below is the own font_6x8
# of the Linux kernel (lib/fonts/font_6x8.c), which is GPL-2.0. Thus this script is
# LICENCE -- READ THIS FIRST. The base bitmap that is embedded below is the font_6x8
# of the Linux kernel itself (lib/fonts/font_6x8.c), which is GPL-2.0. Thus this script is
# GPL-2.0-only, and the PSF that it produces is GPL-2.0-only too. The full licence text is
# beside this script, as scripts/picocalc-lyra/LICENSE.GPL-2.0. The rest of MeshTerm is
# Apache-2.0, and it stays Apache-2.0. The file meshterm8.psf.gz that this script produces
+2 -2
View File
@@ -1034,7 +1034,7 @@ def run_bridge(host: str, port: int, node_name: str) -> int:
# Prefer the hackergadgets meshcore_console helpers. They have the correct board pins and
# the same node identity that the GUI uses. Fall back to a direct setup for a generic
# install (a Waveshare HAT with a runtime from pip), or for the own venv of the bridge on
# install (a Waveshare HAT with a runtime from pip), or for the bridge's own venv on
# a host where the GUI package is older than the runtime.
identity = None
radio = None
@@ -1135,7 +1135,7 @@ def run_bridge(host: str, port: int, node_name: str) -> int:
}
# Use the identity of the GUI first, in the place where the meshcore-uconsole stack
# keeps it. Thus a bridge that runs from its own venv is the same node as the GUI.
# Then use the own identity of the bridge.
# Then use the bridge's own identity.
xdg = Path(env("XDG_DATA_HOME") or (HOME / ".local" / "share"))
for key_path in (
xdg / "meshcore-uconsole" / "identity.key",