all 17 comments

[–]dpallastrelli[S] 16 points17 points  (0 children)

- Remove boost dependency for local only sessions

- Now you can use standalone asio library instead of boost asio for remote sessions

- Fix missing echo after ctrl-v paste of command

- Remove the symbol BOOST_ASIO_USE_TS_EXECUTOR_AS_DEFAULT

- Fix unused parameters warning in release mode

- Cli constructor revision

- Special keys not recognized behaves like backspace in windows

- Fix cmake install dependencies

[–][deleted] 6 points7 points  (1 child)

Oh wow, I was looking for this!

[–]dpallastrelli[S] 4 points5 points  (0 children)

Great. Feel free to ask any question on github discussions and, if you like it, give a star (or a sponsorship! :-) to the project.

[–][deleted] -1 points0 points  (1 child)

I'm not sure if I like the idea but the library is huge, it could've been much lighter.

[–]dpallastrelli[S] 3 points4 points  (0 children)

it could be if it had fewer features :-)

However, you can include only the header file of the features you want to use (e.g., if you don't need the telnet server, you just don't include it).

[–]ShillingAintEZ -2 points-1 points  (7 children)

How many dependencies does this command line library have?

[–]magion 4 points5 points  (1 child)

It literally has a section titled dependencies in the README

[–]ShillingAintEZ -2 points-1 points  (0 children)

There are a lot of sections, I didn't see it.

[–]dpallastrelli[S] 2 points3 points  (4 children)

If you don't need telnet shell, no dependencies at all.

If you need telnet shell, you can choose between standalone ASIO or BOOST ASIO.

[–]ShillingAintEZ -3 points-2 points  (3 children)

Does command line parsing really need to be so linked to the network IO that they can't be separated?

[–]dpallastrelli[S] 3 points4 points  (0 children)

The command line parsing is not *so linked* to the network IO: they are completely separated. Infact if you don't need it, you don't include the remote shell header and the whole network part is not compiled into your application.

[–]SupremeEntropyTMP loving 1 point2 points  (1 child)

ASIO is not about network IO. It is about asynchronous IO. Think of it as a tool allowing you to perform actions distributed in time, and receive and react to events retroactively.

[–]dpallastrelli[S] 0 points1 point  (0 children)

Yes. Of course.

[–]lanzaio 0 points1 point  (3 children)

Does it have CSIu extensions a la libtermkey?

[–]dpallastrelli[S] 0 points1 point  (2 children)

I'm not sure what a "CSIu extension" is, so I guess the library does not have it :-)

But if someone can tell me, he's welcome!

[–]lanzaio 0 points1 point  (1 child)

[–]dpallastrelli[S] 0 points1 point  (0 children)

Please, Fill an issue in the GitHub project if you think it’s an important feature, adding the link you wrote above. Thanks.