uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (Jira)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-6187) Bad line endings for all files UIMA_HOME/bin/*.sh
Date Thu, 06 Feb 2020 22:08:00 GMT

    [ https://issues.apache.org/jira/browse/UIMA-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031980#comment-17031980

Marshall Schor commented on UIMA-6187:

To see which files have cr/lf endings in the repository (or in the working dir), use this
git command:
git grep -I --files-with-matches $'\r' HEAD {code}
or, use the short form
git grip -Il $'\r' HEAD {code}
The HEAD greps inside the repo.  Leave this off to grep in the working directory.

The regexp matches a "windows-style" CR before the end of line.

The "$" in front of the regex is required, because the grep seems to be doing char matching,
not regular-expression matching.  The $'\r' converts this to the carriage return character.

To see which files have cr/lf endings in the working dir, you can use the same command, but
leave off HEAD:
 git grep -Il $'\r' {code}
You can also check parts of the subtree:
git grep -Il $'\r' src/main/scripts {code}

> Bad line endings for all files UIMA_HOME/bin/*.sh 
> --------------------------------------------------
>                 Key: UIMA-6187
>                 URL: https://issues.apache.org/jira/browse/UIMA-6187
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 3.1.1SDK
>            Reporter: Edward Epstein
>            Priority: Major
> All text files in this SDK have CRLF line endings. Linux executable scripts (bin/*.sh)
should not have them.

This message was sent by Atlassian Jira

View raw message