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 man page or info doc #66

Open
ghost opened this issue Jun 13, 2017 · 4 comments
Open

No man page or info doc #66

ghost opened this issue Jun 13, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Jun 13, 2017

This issue report is based on using this JAR.

Norma follows the second convention described here, which is fair enough, but its output is excessive:

$ java -jar norma-0.5.0-SNAPSHOT-jar-with-dependencies.jar 2>&1 | wc -l
614

Users should not be expected to wade through 600+ lines of "help". Ideally, for usability, the help output should fit onto a single screen (~24 lines).

Additional information should be portioned off into one or more man pages or info files.

@petermr
Copy link
Member

petermr commented Jun 15, 2017

Closed as out of current scope

@jkbcm
Copy link
Contributor

jkbcm commented Jun 15, 2017

I think this could be something to address when delivering current projects. As a new user it slowed me down in getting started with the tools and gives a rather unwelcoming first impression which we would benefit from improving on. The issue with incorrect line-endings characters also affects this -- my shell prompt is left in the wrong place on Ubuntu (not returned the left), which is something we could fix as a quick win.

@ghost
Copy link
Author

ghost commented Jun 15, 2017

@petermr wrote:

Closed as out of current scope

This issue has not been assigned to a scope, so that is not a valid reason to close it.

In any case, I completely agree with @jkbcm that there is potential for quick, incremental, tidy-as-you-go improvements to be made within current projects, that would ameliorate - if not altogether resolve - issues like this.

@ghost
Copy link
Author

ghost commented Jun 21, 2017

When this issue comes to be addressed, it may be useful to consult the Gnits Standards for Command Line Interfaces, and possibly also the corresponding GNU standards.

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

No branches or pull requests

2 participants