>I made another commit so that .kt and .kts files are treated as text

Frankly speaking, we have  * text=auto which means git would treat all
files as text if their first 8000 bytes does not have 00 byte.
In other words, kt files were already treated as text files.

>gradlew, sqlline, sqlsh

That indeed makes sense.

>I am still having trouble starting sqlline and sqlsh. I get
>ClassNotFoundException. I suspect the classpath-in-a-jar trick doesn't
>work on Windows/Cygwin.

That is strange, as classpath-jar is a very common trick to shorten the
command line.
I don't have Cygwin setup though.

What appears in Class-Path attribute in your case?

>I also wish Autostyle weren't so picky about line endings. Javac etc.
>ignore them, so Autostyle should too.

I see it might be painful, however:
a) Test cases are often full of `isLinux` to deal with LF vs CRLF in test
outputs.
b) Git makes it extremely hard to fix "improperly committed files" (e.g.
see
https://www.edwardthomson.com/blog/advent_day_21_renormalizing_line_endings.html
 )

Of course, we do have .gitattributes, so we are likely protected from
committing wrong data to the repository,
however, if your local file does not correspond to Git expectations, then
Git **won't** complain.

Sample:
$ unix2dos core/build.gradle.kts # in macOS files are expected to have LF
endings
$ git diff
warning: CRLF will be replaced by LF in core/build.gradle.kts.
The file will have its original line endings in your working directory

^^ diff does not show the file as "modified".
If the file is included as a test sample, then users might be surprised by
the results.


In other words:
A) I expect that Autostyle verifications are fully compatible with Git
clones.
In other words, if the repository was cloned via standard Git approaches,
then Autostyle won't complain.

B) Autostyle will complain if the checkout folder is moved to another OS.
For instance, if someone downloads source_release.zip, then the files can't
be compatible with both LF and CRLF.
I'm not sure it is a common case though.

Do you have other suggestions?

Vladimir

Reply via email to