CLI autocomplete

RE: CLI autocomplete

schef — Thu, 03 Aug 2017 13:27:17 GMT

Very good :)

RE: CLI autocomplete

Jakub Rzeszutko — Thu, 03 Aug 2017 13:25:38 GMT

First blog post is available here :)

devzone.nordicsemi.com/.../

RE: CLI autocomplete

Jakub Rzeszutko — Thu, 03 Aug 2017 11:11:08 GMT

Hi,

New CLI is available with released (today) SDK14.

I encourage you to try few examples like: cli, ble_app_cli and few others

RE: CLI autocomplete

Jakub Rzeszutko — Wed, 24 May 2017 08:45:22 GMT

Please be patient ;)

RE: CLI autocomplete

schef — Wed, 24 May 2017 08:39:25 GMT

Cool! I'm very excited :) is there any beta testing? :D

RE: CLI autocomplete

Jakub Rzeszutko — Wed, 24 May 2017 07:38:27 GMT

User will have two macro types: one for creating "root command" and other for creating subcommands. We plan to ensure backward compatibility so either root command can have a handler as it is now or sub commands can have it. Console will execute deepest handler which will be found.

As an example you can have command: "log enable SPI" where:

log (root command): can have handler or not
enable (sub command of log): can have handler or not
SPI (sub command of enable): can have handler or not.

So you can either implement very complex handler for "log" to detect "enable" and next "SPI" or less complex handler for "enable" to detect "SPI" or you can implement only a simple handler for "SPI".

RE: CLI autocomplete

schef — Wed, 24 May 2017 07:16:50 GMT

What is recomended way of writing commands so it will be compatible in the future. I mean about the depth autocomplete?

Now i have alot of if/else if/else which is not very readable.

RE: CLI autocomplete

Jakub Rzeszutko — Tue, 23 May 2017 12:10:57 GMT

I promise there will be a blog regarding new features but not before release of new console. I am also quite sure that you will like what we prepared :)

RE: CLI autocomplete

schef — Tue, 23 May 2017 11:24:56 GMT

A thread is already a good start!

RE: CLI autocomplete

Jakub Rzeszutko — Tue, 23 May 2017 11:23:17 GMT

Hi endnode, I will try but we are very short on time :(

RE: CLI autocomplete

schef — Tue, 23 May 2017 11:15:15 GMT

In putty it works great! Thanks.

RE: CLI autocomplete

endnode — Tue, 23 May 2017 11:10:56 GMT

(Hi Jakub, this almost screams like "write a blog post about me!":)

RE: CLI autocomplete

Jakub Rzeszutko — Tue, 23 May 2017 10:55:36 GMT

Hi, Regarding first concern. Pressing "up" shall print in command line historical command starting from last entered. If command "history" is showing for example:

[ 0] cmd_0
[ 1] cmd_1
[ 2] cmd_2
[ 3] cmd_3

than by pressing "up" you will see cmd_3, "up" again and you will see cmd_2 and so on... But in the example you can observe following bug: if you have commands from [ 0] to [ 7] and if you will press "up" as many times to see what was cmd [ 0] than CLI will be blocked until .

After pressing copletion shall be done automatically without any additional . If you need to press enter to see completion results it means that your terminal is not correctly configured. I will try to paste my putty settings here.

RE: CLI autocomplete

schef — Tue, 23 May 2017 10:15:47 GMT

I have just tried out what would happend if i pressed two times and press . It did use the two commands back in history. Is this normal behavior? Should i always press enter also after pressing ?

RE: CLI autocomplete

Jakub Rzeszutko — Tue, 23 May 2017 10:03:23 GMT

So it will be easy from here to make it working as you expect :) My recommendation is to do following in case of RTT:

open connection using JLink.exe (not JLink viewer!)
as terminal please use Putty. It is the only terminal I found which can be easly configured to handle VT100 escape codes. Mandatory Putty configuration:
inside Terminal->Line discipline options-> Local echo and local line editiong set to: "Force off"
Terminal->Keybord: you shall have set: Control-H, rxvt, SCO, Normal, Normal

RE: CLI autocomplete

schef — Tue, 23 May 2017 09:54:41 GMT

I'm using RTT. I'm on linux and am using SEGGER J-Link Commander V6.12e for connection to J-Link and telnet localhost 19021 for communication.

Executing history command works. But on arrow keys i get:

nrf_cli:~$ ^[[A^[[A^[[B^[[A^[[B^[[A.

Maybe this has to do with telnet.

RE: CLI autocomplete

Jakub Rzeszutko — Tue, 23 May 2017 09:50:54 GMT

What do you mean not working? When I am flashing this hex to my board I am able to:

Execute command: "history"
Use up and down arrow to go through history list*

Unofrtunately in this version is small bug in the code. If history list is full [0-7] and when you will press up arror until you will see history cmd [0], console will be blocked until you will press enter. This will be fixed with new CLI release.

What interface are you using? UART, USB or RTT?

RE: CLI autocomplete

schef — Tue, 23 May 2017 09:45:02 GMT

I am using this one. But the history is not working there.

RE: CLI autocomplete

Jakub Rzeszutko — Tue, 23 May 2017 09:14:50 GMT

Hi, Example is available here: \examples\peripheral\cli\

RE: CLI autocomplete

schef — Tue, 23 May 2017 08:57:54 GMT

This is very good news. :) You said that and history is already implemented. Is there a example or can u share how to use them already?

RE: CLI autocomplete

Jakub Rzeszutko — Tue, 23 May 2017 08:45:21 GMT

Hello schef, Command line interface which is in SDK13 already have some of these features. Tab button provides completition of existing commands, up and down arrows allows you to go through history.

We are currently working to introduce more advanced console application and we will try to add it with next SDK release. New features which you can expect:

handling left and right arrows,
handling home, end, insert button,
multi level commands with smart completion of each level,
optimized memory usage,
cooperation with log module - console will be able to display logs and introduce new commands in parallel,
user will have possibility to dynamically enable and disable logs

Basically we want to provide really user friendly CLI.

Recommended Putty settings for RTT connection:

RE: CLI autocomplete

endnode — Tue, 23 May 2017 08:27:06 GMT

What command line interface are you talking about?:)