[
https://issues.apache.org/jira/browse/UIMA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488682
]
Thilo Goetz commented on UIMA-373:
----------------------------------
Many people do in fact use .sh as script file extension, and it is considered a
best practice by some. I don't personally like files without extensions very
much, as it's even harder to know what they are.
Don't you think we can expect our users to make the leap from "cpeGui shell
script" cpeGui.bat or cpeGui.sh, depending on the platform? I think users who
don't manage to make that connection by themselves will have a very hard time
with the rest of UIMA. And while we're on the topic of "typically": command
names typically don't use camel case. So there ;-)
> UIMA's Unix command line utilities are named badly
> --------------------------------------------------
>
> Key: UIMA-373
> URL: https://issues.apache.org/jira/browse/UIMA-373
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Environment: Unix
> Reporter: Eddie Epstein
>
> UIMA command line utilities are available in two flavors: commandName.bat for
> Windows and commandName.sh for Unix. The Unix world typically does not use an
> extension for scripts.
> In addition to looking dumb, my real peeve with the .sh extension is how it
> complicates writing documentation, saying things like "using the cpeGui shell
> script (cpeGui.bat on Windows, cpeGui.sh on Unix)". Dropping .sh would allow
> the documentation to just say "using commandName".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
