-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Commandline help text not correct (e.g., "-f,--fetch <FILE>" does not use a file) #2016
Comments
Let me add that fetching alone will not do much. It will fetch, but the results will cease to exist when the invocation terminates. To get actual output, the fetch command should be chained with Having said that, the documentation can certainly be improved. @baderas: Could you provide a pull request? Improving the textual output of the command line is certainly a good entry point. |
We think that the command line should be |
I just noticed that this issue is in a sense a duplicate of #1850. I am closing the older one and we can track further discussion here. |
If no one is working on this issue, may I fix it? Thanks |
@dhananjaya2007 Sure go ahead |
The point is that Apache Commons (library currently used) prints the argument(s) within the symbols "<" and ">". So, if we want to show the CLI help like above, it would be easy. In another case, I can program a new code for this. |
@davidemdot Looks good to me. The argument to |
Thanks to @davidemdot this issue is now fixed in the lastest master. We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version. |
JabRef version 3.5 Windows 10 x64
Steps to reproduce:
java -jar JabRef-3.5.jar -h
See http://help.jabref.org/en/CommandLine
<FILE>
is always used as argument name. This is wrong for some command line items, for example-f,--fetch <FILE>
is used as"--fetch=Medline:cancer"
. The correct help entry would be-f, --fetch <SearchTerm>
with an explanation how<SearchTerm>
must be used.For some arguments a filename and some additional information (separated by comma, e.g., for
-i
) can be given.<FILE>
is also not correct there.Same problem exists for:
The text was updated successfully, but these errors were encountered: