You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a priority for me, but since it's been asked, this ticket is to document the work that would be required for initiative.sh to run effectively at the command line.
The first several months of development took place as a CLI app before I ported it to WebAssembly, so the core crate (encompassing the bulk of the logic: command parsing, character generators, etc.) ran and continues to run well at the command line. However, the cli crate is no longer at parity with the web crate, missing the following features:
Note that there are two command-line interfaces, rich (the default) and light (used when the input is not a tty, eg. if you run echo npc | cargo run). There is not currently a switch or configuration option to force a particular interface.
The text was updated successfully, but these errors were encountered:
Hey there! Love what you're doing with the project, but I'm kind of a command line junky. Are you still open to help bringing the CLI up to parity with the web crate?
I have a pull request that adds support for the autocomplete popup, if you'd like to take a gander.
This is not a priority for me, but since it's been asked, this ticket is to document the work that would be required for initiative.sh to run effectively at the command line.
The first several months of development took place as a CLI app before I ported it to WebAssembly, so the
core
crate (encompassing the bulk of the logic: command parsing, character generators, etc.) ran and continues to run well at the command line. However, thecli
crate is no longer at parity with theweb
crate, missing the following features:Note that there are two command-line interfaces,
rich
(the default) andlight
(used when the input is not a tty, eg. if you runecho npc | cargo run
). There is not currently a switch or configuration option to force a particular interface.The text was updated successfully, but these errors were encountered: