Normalize how commands work, debugging #77

tony · 2017-11-09T18:09:38Z

Restructure how commands are passed in

This will probably be by creating a command factory where the command is built, then an execute() for it. But to the user in a tmux object, .cmd should still execute immediately, _cmd() could leave an object where the user can see the exact command tmux is running before hand.

There should be more options to toggle debug settings

The text was updated successfully, but these errors were encountered:

tmux_cmd initialization composes the command the command will be available in the instance attribute .cmd .execute() instance method will run tmux_cmd see Server.cmd for example of new usage Related #77

stale · 2018-01-08T19:03:33Z

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.

This bot is used to handle issues where the issue hasn't been discussed or
has gone out of date. If an issue isn't resolved and handled in a certain
period of time, it may be closed. If you would like your issue re-opened,
please create a fresh issue with the latest, up to date information and
mention this issue in it.

tmux_cmd initialization composes the command the command will be available in the instance attribute .cmd .execute() instance method will run tmux_cmd see Server.cmd for example of new usage Related #77

tony mentioned this issue Nov 10, 2017

Split init / exec of tmux_cmd for debuggability #79

Open

stale bot added the stale label Jan 8, 2018

stale bot closed this as completed Jan 15, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Normalize how commands work, debugging #77

Normalize how commands work, debugging #77

tony commented Nov 9, 2017

stale bot commented Jan 8, 2018

Normalize how commands work, debugging #77

Normalize how commands work, debugging #77

Comments

tony commented Nov 9, 2017

stale bot commented Jan 8, 2018