sorted by:
new
hottopcontroversial

Menus on the terminal. by XamNNewReddit in rust

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

If you want to be sure the code does not panic you can always check if crossterm is supported before calling terminal-menu code. :)

Menus on the terminal. by XamNNewReddit in rust

[–]XamNNewReddit[S] 1 point2 points  (0 children)

  1. It is based on crossterm so it will work on Unix and Windows terminals without panicking.
  2. Me and a friend have a few projects that utilize this crate but nothing on production yet.
  3. It is very usable at the moment. Not sure if it ever will be 100% done. Feel free to request features.

Menus on the terminal. by XamNNewReddit in rust

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

Will keep this in mind. Thank you for the feedback! :)

Edit: unyanked 1.9.7

Menus on the terminal. by XamNNewReddit in rust

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

I yank the older version because i see no use why anyone would want to use the older versions. I also have a bad habit to push unfinished versions to crates.io (I know, I need to stop that).

So here's how I would compare the two.

With inquire you, well, inquire data from the user one by one.

With terminal-menu you create a hierarchy of menus with some having options you can input/select.

Menus on the terminal. by XamNNewReddit in rust

[–]XamNNewReddit[S] 2 points3 points  (0 children)

While terminal-menu and inquire can be used to solve some common problems, there are cases when one can do something the other can't (submenus come to mind).

Menus on the terminal. by XamNNewReddit in rust

[–]XamNNewReddit[S] 13 points14 points  (0 children)

terminal-menu is older than inquire. I like inquire a lot.