← index #13532Issue #8828
Related · high · value 0.169
QUERY · ISSUE

Verbosity of mpremote commands should be manageable and shouldn't go to stdout

openby Tico06opened 2024-01-27updated 2025-09-05
bugtools

Hi There,

This is related to #8828.

I'd suggest verbosity of mpremote commands should be manageable with an option like -q (quiet) or -v (verbosity), and should not go to stdout but stderr preferably.

This would allow to script mpremote and retrieve some information from the device like:

$> mpremote -q connect /dev/ttyACM0 resume + mount . + exec "import machine;print(machine.unique_id())" > deviceID.txt
$> cat deviceID.txt
16600659686507361317
$>

At the present, it looks more than this:

$> mpremote connect /dev/ttyACM0 resume + mount . + exec "import machine;print(machine.unique_id())" > deviceID.txt
$> cat deviceID.txt
16600659686507361317
Local directory . is mounted at /remote
$>

Thanks and best regards,

Eric.

CANDIDATE · ISSUE

mpremote should not echo command when writing file to stdout

closedby bulletmarkopened 2022-06-28updated 2024-01-26
enhancementtools

Here is an example of the problem:

$ mpremote cat main.py
cat :main.py
print('hello world')

mpremote should not echo the cat :main.py because it corrupts the output of the actual file contents, e.g. if you pipe it somewhere.

MicroPython 1.19.1 on ESP32.

Keyboard

j / / n
next pair
k / / p
previous pair
1 / / h
show query pane
2 / / l
show candidate pane
c
copy suggested comment
r
toggle reasoning
g i
go to index
?
show this help
esc
close overlays

press ? or esc to close

copied