Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certain options cause rtm-cli to not print output (or execute commands?) #15

Open
paulstodghill opened this issue Mar 14, 2019 · 3 comments

Comments

@paulstodghill
Copy link

I recently upgraded to version 1.5.1. Previously, I was able to use the "-p" and "-s" options to simplify the output when running on a dumb terminal (e.g., Emacs shell buffer). Now, when I use these options (and "-c"), even under a "normal" terminal window (e.g., xterm, Gnome Terminal), rtm prints neither the "Logged In As" message nor the ">" prompt. Typing in commands (e.g., "add task1") does not appear to work.

$ rtm
Logged In As: XXXXXXXX
> quit
$ rtm -c
[ no output after minutes ]

Interestingly, it does respond to CTRL-D (Unix end-of-file) and exits with a successful status.

I observe this behavior both under Linux and MacOS.

$ npm --version
6.9.0
$ rtm --version
1.5.1
$
@dwaring87
Copy link
Owner

Thanks for pointing this out. It looks like I introduced this bug in the last update. With a flag present but no command given, it doesn't start the interactive mode like it should.

Until this is fixed, you can still start the interactive mode with just rtm and then add the flag to the first command in the interactive mode (ie ls -p). The flags are "sticky" in the sense that all subsequent commands in the session will have the flag set.

@paulstodghill
Copy link
Author

Excellent. Thank you for the workaround.

@paulstodghill
Copy link
Author

Whoops. Hit the wrong button. Sorry about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants