Everlooping interrupts good offline workflow

[iceman1001]

The ever wait introduced for some commands is kind of disturbing the flow of taking the pm3 with bt add-on offline from client, go away , do simulating and come back to reconnect...

Then the everlooping waittimout hinders it. This is why always ack, or being in interactive mode vs cli, is good.

[doegox]

I think it's something to discuss with doegox/proxmark-internal#76 to get a coherent approach. For me it's not yet clear how to achieve all scenarios at once:

• initiate commands from -s/-c/-l or interactively
• interrupt command by button press or kbd press
• allow for BT to go far away, to loose the connection and to reconnect when being close again (automatically when we're in a running command?)
• it button or kbd was pressed when connection was lost, resync when in BT range again ?

[iceman1001]

Aha, yes, I knew I saw something about it. totally forgot it.