User Interface
Noodle has a command line interface. Here’s the documentation for all noodle commands.
Command names are meant to be clear and descriptive. There are some aliases for speed even though autocomplete is a good friend. Further aliasing and soft input should be handled by a language model of some kind. Noodle currently aims to implement only the core functionality with a hard interface.
Noodle tries not to impose on the user’s use case. The basic workflow of noodle just has to do with its inherent structure and the core elements of its interface.
When you open noodle, it runs a refresh which brings it up to date with the current state of the working directory. You may be prompted to deal with conflicts, deleted files, duplicate file names, new files etc. But noodle tries to stay out of your hair.
After the refresh, you can manipulate the multiplex graph however you like. You interact with your noodle using commands. Noodle executes the command and displays feedback to show you how the state of the noodle has changed. Some commands only change how information is displayed rather than the structure itself.
Many commands use the current selection of doodles, the layermask, and/or the current layer as implicit parameters. Make sure you’re aware of the state of these UI elements.
Making use of the optional quick command can help speed up workflow too.
Noodle does not save any changes you make until you quit or save.
In bash you can exit noodle without saving by cancelling the program with Ctrl + C.