#452 Send settings per pre-defined command

[Anonymous]

It might be beneficial if the send settings (Terminal settings->Text settings) could be set per-pre defined command. This would allow, for example, to define multi-line commands which wait for replies and commands that are sent without delay without having to change the global terminal settings.

Example:

• Command1 is used to probe whether a device is alive. Having the terminal freeze whenever no reply is received because the device might not have started up properly can be annoying.
• Command2 is a multi-line command sequence used to execute a test on the device. After each command, waiting for the reply or inserting a delay might be necessary for the test to be executed successfully.

[Maettu]

Ticket moved from /p/y-a-terminal/bugs/518/ as this rather is an FR than a bug.

[Maettu]

Clarification with PMi:

Needed is enable/disable of send/receive relevant settings, those that do not result in reformatting:

• AddDelay
• WaitForResponse
• TextExclusion
• (Glue?)

Line breaks not, reformatting for sure.

Possible implementation:

• Dedicated \!(WaitForResponseOn)/\!(WaitForResponseOff) keywords
• A settings specific \!(WaitForResponse(On|Off)) keyword
• Generic e.g. \!(Enable(WaitForResponse)) keyword
• Even more generic e.g. \!(Setting(WaitForResponse, On|Off)) keyword

A dedicated approach would be fast and straight-forward to implement. A generic approach would be more future-proof to potentially cover any setting. A two-step approach is probably the best way to go:

1. Dedicated keywords what is needed now.
2. Generic keywords in long-term.

[Maettu]

Possibility to quickly allow changing ASCII control char radix has been requested in FR #462 mixed radix related email discussion, i.e. \!(Setting(...Radix, Str|Hex|...)).