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

"No file open" error message #4

Open
ms609 opened this issue Mar 30, 2020 · 1 comment
Open

"No file open" error message #4

ms609 opened this issue Mar 30, 2020 · 1 comment
Labels
interface Problems with behaviour of input/output

Comments

@ms609
Copy link

ms609 commented Mar 30, 2020

On writing this issue I've read the output more carefully: I was getting confused that options set before open = were being ignored. Now I have spotted the No file open message that addseq = , nreps = , and ratchet = output.

Could this message be made more explicit? e.g. No file open: setting not changed? If nothing else, a longer string would be more noticable and I'd be less likely to overlook it!

@mbrazeau
Copy link
Owner

Possibly. However, none of those commands exclusively require a file to be open, so this can eventually be changed to be set regardless of whether a file is open.

@mbrazeau mbrazeau added the interface Problems with behaviour of input/output label Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interface Problems with behaviour of input/output
Projects
None yet
Development

No branches or pull requests

2 participants